From: mame@...
Date: 2015-05-03T10:36:33+00:00
Subject: [ruby-core:69063] [Ruby trunk - Bug #11116] [Open] The spec of	String#dump

Issue #11116 has been reported by Yusuke Endoh.

----------------------------------------
Bug #11116: The spec of String#dump
https://bugs.ruby-lang.org/issues/11116

* Author: Yusuke Endoh
* Status: Open
* Priority: Normal
* Assignee: Yusuke Endoh
* ruby -v: ruby 2.2.1p85 (2015-02-26 revision 49769) [x86_64-linux]
* Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN, 2.2: UNKNOWN
----------------------------------------
The current spec says:

     call-seq:
       str.dump   -> new_str

    Produces a version of +str+ with all non-printing characters replaced by
    <code>\nnn</code> notation and all special characters escaped.

      "hello \n ''".dump  #=> "\"hello \\n ''\"

`\nnn` must be `\xnn` now.

In addition, I've expected String#dump to return a string that evaluates to an original string (except singleton methods, object id, etc.) when `eval`ed.  Is this a right expectation?  If so, it would be good to officially include the mention in the spec.  What do you think?

-- 
Yusuke Endoh <mame@ruby-lang.org>



-- 
https://bugs.ruby-lang.org/