ruby-core@ruby-lang.org archive (unofficial mirror)
 help / color / mirror / Atom feed
From: "byroot (Jean Boussier) via ruby-core" <ruby-core@ml.ruby-lang.org>
To: ruby-core@ml.ruby-lang.org
Cc: "byroot (Jean Boussier)" <noreply@ruby-lang.org>
Subject: [ruby-core:117249] [Ruby master Feature#20350] Return chilled string from Symbol#to_s
Date: Wed, 20 Mar 2024 08:58:11 +0000 (UTC)	[thread overview]
Message-ID: <redmine.journal-107337.20240320085811.11019@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-20350.20240319210642.11019@ruby-lang.org

Issue #20350 has been updated by byroot (Jean Boussier).


To provide some data-point. Our monolith runs with https://github.com/Shopify/symbol-fstring, which makes the return value of `Symbol#to_s` frozen without any problem. I think we had to fix a single gem to make it work a few years back, that's it.

That said, while we run a lot of code (700+ transitive gems), that's not necessarily fully representative of the code out there.

Also one major difference with chilled string literals is that you can't just set `RUBYOPT="--disable-frozen-string-literal"` to continue running older code. I guess you could monkey patch `String#to_s` though, and provide that as a gem to make it easy to provide backward compatibility.

All this to say that as a Ruby user, I'd like this change to happen, because `Symbol#to_s` is a major source of allocation, and Ruby performance is very GC dependent.

But as a Ruby committer I think we need to be careful about the rate of deprecation and backward compatibility breaks. On one hand it would sound logical to ship such change at the same time as the change for frozen string literals, but on the other hand it makes the jump bigger and may alienate some users. So it's a fine line to walk.

So I'm positive, but with some reservations.

----------------------------------------
Feature #20350: Return chilled string from Symbol#to_s
https://bugs.ruby-lang.org/issues/20350#change-107337

* Author: Dan0042 (Daniel DeLorme)
* Status: Open
----------------------------------------
During Ruby 2.7 development there was an attempt to return a frozen string from Symbol#to_s (#16150#note-22)

This had to be rolled back due to incompatibility, but now we have chilled strings (#20205)

Symbol#to_s can safely return a chilled string, giving developers time to fix warnings before switching to a frozen string.




-- 
https://bugs.ruby-lang.org/
 ______________________________________________
 ruby-core mailing list -- ruby-core@ml.ruby-lang.org
 To unsubscribe send an email to ruby-core-leave@ml.ruby-lang.org
 ruby-core info -- https://ml.ruby-lang.org/mailman3/postorius/lists/ruby-core.ml.ruby-lang.org/

  reply	other threads:[~2024-03-20  8:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-19 21:06 [ruby-core:117240] [Ruby master Feature#20350] Return chilled string from Symbol#to_s Dan0042 (Daniel DeLorme) via ruby-core
2024-03-20  8:58 ` byroot (Jean Boussier) via ruby-core [this message]
2024-03-20 10:52 ` [ruby-core:117255] " Eregon (Benoit Daloze) via ruby-core
2024-04-03 10:45 ` [ruby-core:117430] " Eregon (Benoit Daloze) via ruby-core
2024-04-16  6:30 ` [ruby-core:117524] " ko1 (Koichi Sasada) via ruby-core
2024-04-16  6:41 ` [ruby-core:117526] " byroot (Jean Boussier) via ruby-core
2024-04-17 22:44 ` [ruby-core:117579] " matz (Yukihiro Matsumoto) via ruby-core

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.journal-107337.20240320085811.11019@ruby-lang.org \
    --to=ruby-core@ruby-lang.org \
    --cc=noreply@ruby-lang.org \
    --cc=ruby-core@ml.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).