From bd6c300525af1e6d59f17f0e13d92a20bc8e46ab Mon Sep 17 00:00:00 2001 From: Jean Boussier Date: Fri, 13 Dec 2024 09:32:37 +0100 Subject: [PATCH] Clarify chilled stirng behavior in 3.4.0-rc1 release announcement Identical to the preview2 release: https://github.com/ruby/www.ruby-lang.org/pull/3380 --- en/news/_posts/2024-12-12-ruby-3-4-0-rc1-released.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/en/news/_posts/2024-12-12-ruby-3-4-0-rc1-released.md b/en/news/_posts/2024-12-12-ruby-3-4-0-rc1-released.md index 339f52d1a9..bbbce49821 100644 --- a/en/news/_posts/2024-12-12-ruby-3-4-0-rc1-released.md +++ b/en/news/_posts/2024-12-12-ruby-3-4-0-rc1-released.md @@ -36,8 +36,8 @@ Switch the default parser from parse.y to Prism. [[Feature #20564]] ## Language changes -* String literals in files without a `frozen_string_literal` comment now behave - as if they were frozen. If they are mutated a deprecation warning is emitted. +* String literals in files without a `frozen_string_literal` comment now emit a deprecation warning + when they are mutated. These warnings can be enabled with `-W:deprecated` or by setting `Warning[:deprecated] = true`. To disable this change, you can run Ruby with the `--disable-frozen-string-literal` command line argument. [[Feature #20205]]