ruby-core@ruby-lang.org archive (unofficial mirror)
 help / color / mirror / Atom feed
From: michael@grosser.it
To: ruby-core@ruby-lang.org
Subject: [ruby-core:92842] [Ruby trunk Bug#15876] 1.to_s.encoding != Encoding.default_internal
Date: Sat, 25 May 2019 17:40:04 +0000 (UTC)	[thread overview]
Message-ID: <redmine.issue-15876.20190525174004.3506be98c64473a3@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-15876.20190525174004@ruby-lang.org

Issue #15876 has been reported by grosser (Michael Grosser).

----------------------------------------
Bug #15876: 1.to_s.encoding != Encoding.default_internal
https://bugs.ruby-lang.org/issues/15876

* Author: grosser (Michael Grosser)
* Status: Open
* Priority: Normal
* Assignee: 
* Target version: 
* ruby -v: 2.6.3
* Backport: 2.4: UNKNOWN, 2.5: UNKNOWN, 2.6: UNKNOWN
----------------------------------------
I ran into strange looking test output when I compared .to_s with an expected text, saying that the encoding was different, which is confusing/annoying especially to users that don't know how encodings work in ruby.
1.to_s.encoding should be the same as "".encoding



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

       reply	other threads:[~2019-05-25 17:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <redmine.issue-15876.20190525174004@ruby-lang.org>
2019-05-25 17:40 ` michael [this message]
2019-05-25 22:25 ` [ruby-core:92843] [Ruby trunk Bug#15876] 1.to_s.encoding != Encoding.default_internal shevegen
2019-05-26  0:34 ` [ruby-core:92845] " mame
2019-05-26  2:30 ` [ruby-core:92846] " duerst
2019-05-26  3:08 ` [ruby-core:92847] " mame
2019-05-31 16:10 ` [ruby-core:92913] " naruse
2019-05-31 17:37 ` [ruby-core:92914] " hanmac
2019-05-31 20:29 ` [ruby-core:92917] " eregontp

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.ruby-lang.org/en/community/mailing-lists/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=redmine.issue-15876.20190525174004.3506be98c64473a3@ruby-lang.org \
    --to=ruby-core@ruby-lang.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).