Advent of Changelog: Day 21

Author: zverok

2.4.md

@@ -16,9 +16,9 @@ description: Ruby 2.4 full and annotated changelog
  -->
 
 * **Released at:** Dec 25, 2016 (<a class="github" href="https://github.com/ruby/ruby/blob/trunk/doc/NEWS-2.4.0">NEWS</a> file)
-* **Status (as of Feb 04, 2023):** EOL, latest is 2.4.10
+* **Status (as of Dec 21, 2023):** EOL, latest is 2.4.10
 * **This document first published:** Oct 14, 2019
-* **Last change to this document:** Feb 04, 2023
+* **Last change to this document:** Dec 21, 2023
 
 ## Highlights[](#highlights)
 
@@ -189,6 +189,7 @@ New single-method module was introduced, meant to be overridden in order to cont
     ```
   * In Ruby 2.7, new methods [were added](2.7.html#warning-and-) to `Warning` module allowing control over per-category warning suppression;
   * In Ruby 3.0, category support [was improved](3.0.html#warningwarn-category-keyword-argument).
+  * [3.3](3.3.html#new-warning-category-performance): added new warning category: `:performance`.
 
 ### `Object#clone(freeze: false)`[](#objectclonefreeze-false)
 

2.7.md

@@ -8,9 +8,9 @@ description: Ruby 2.7 full and annotated changelog
 # Ruby 2.7
 
 * **Released at:** Dec 25, 2019 (<a class="github" href="https://github.com/ruby/ruby/blob/ruby_2_7/NEWS">NEWS</a> file)
-* **Status (as of Sep 20, 2023):** 2.7.8 is EOL
+* **Status (as of Dec 21, 2023):** 2.7.8 is EOL
 * **This document first published:** Dec 27, 2019
-* **Last change to this document:** Sep 20, 2023
+* **Last change to this document:** Dec 21, 2023
 
 <!-- TODO: all links to docs should be replaced with /2.7.0/ suffix instead of /master/ when 2.7.0 would be published -->
 
@@ -121,7 +121,9 @@ In block without explicitly specified parameters, variables `_1` through `_9` ca
   # %w[test me].each { _1.each_char { p _1 } }
   #                    ^~
   ```
-* **Follow-up:** Warning on attempt to assign to numbered parameter [became errors in 3.0](3.0.html#other-changes).
+* **Follow-ups:**
+  * [3.0](3.0.html#other-changes): Warning on attempt to assign to numbered parameter became errors.
+  * [3.3](3.3.html#standalone-it-in-blocks-will-become-anonymous-argument-in-ruby-34): a warning introduced indicating that in Ruby 3.4, `it` would become an alternative anonymous block parameter (only one, same as `_1`). There is no plan to deprecate numbered parameters.
 
 ### Beginless range[](#beginless-range)
 
@@ -799,6 +801,7 @@ Like `Array#union` and `#difference`, [added](2.6.html#arrayunion-and-arraydiffe
   map[1]
   # => nil  -- value successfully collected, even if key was not GC-able
   ```
+* **Follow-ups:** [3.3](3.3.html#objectspaceweakkeymap): A new class `ObjectSpace::WeakKeyMap` introduced, more suitable for common use-cases of a "weak mapping." It only has garbage-collectable keys.
 
 ### `Fiber#raise`[](#fiberraise)
 
@@ -1028,7 +1031,7 @@ Allows to emit/suppress separate categories of warnings.
   ```
 * **Notes:**
   * The only existing categories currently are `:deprecated` (covers all deprecations) and `:experimental` (as of 2.7, covers only pattern matching)
-  * Note that turning of `:deprecated` warning will also mute the warning of features which was deprecated explicitly in your code, for example with <a class="ruby-doc" href="https://ruby-doc.org/core-2.7.0/Module.html#method-i-deprecate_constant"><code>Module#deprecate_constant</code></a>
+  * Note that turning off `:deprecated` warning will also mute the warning of features which was deprecated explicitly in your code, for example with <a class="ruby-doc" href="https://ruby-doc.org/core-2.7.0/Module.html#method-i-deprecate_constant"><code>Module#deprecate_constant</code></a>
     ```ruby
     class HTTP
       NOT_FOUND = Exception.new
@@ -1041,7 +1044,9 @@ Allows to emit/suppress separate categories of warnings.
     # ...no warning issued...
     ```
   * Another way to turn on and off separate categories of warnings is passing `-W:(no-)<category>` flag to ruby interpreter, e.g. `-W:no-experimental` means "no warnings when using experimental features".
-* **Follow-up:** In Ruby 3.0, it was [allowed for user code](3.0.html#warningwarn-category-keyword-argument) to specify warning category, and intercept it.
+* **Follow-ups:**
+  * [3.0](3.0.html#warningwarn-category-keyword-argument): user code is allowed to specify warning category, and intercept it;
+  * [3.3](3.3.html#new-warning-category-performance): added new warning category: `:performance`.
 
 ## Standard library[](#standard-library)
 

3.0.md

@@ -8,9 +8,9 @@ description: Ruby 3.0 full and annotated changelog
 # Ruby 3.0
 
 * **Released at:** Dec 25, 2020 (<a class="github" href="https://github.com/ruby/ruby/blob/ruby_3_0/NEWS.md">NEWS.md</a> file)
-* **Status (as of Sep 20, 2023):** 3.0.6 is security maintenance (will EOL soon!)
+* **Status (as of Dec 21, 2023):** 3.0.6 is security maintenance (will EOL soon!)
 * **This document first published:** Dec 25, 2020
-* **Last change to this document:** Sep 20, 2023
+* **Last change to this document:** Dec 21, 2023
 
 ## Highlights[](#highlights)
 
@@ -960,6 +960,7 @@ Just fixes an inconsistency introduced by optimization many versions ago.
   processed.lambda? # => false
   processed.call    # => "nil", it is really still not a lambda
   ```
+* **Follow-ups:** [3.3](3.3.html#kernellambda-raises-when-passed-proc-instance): The warning was turned into an exception.
 
 #### `Proc#==` and `#eql?`[](#proc-and-eql)
 

3.2.md

@@ -8,9 +8,9 @@ description: Ruby 3.2 full and annotated changelog
 # Ruby 3.2
 
 * **Released at:** Dec 25, 2022 (<a class="github" href="https://github.com/ruby/ruby/blob/ruby_3_2/NEWS.md">NEWS.md</a> file)
-* **Status (as of Dec 20, 2023):** 3.2.2 is current _stable_
+* **Status (as of Dec 21, 2023):** 3.2.2 is current _stable_
 * **This document first published:** Feb 4, 2022
-* **Last change to this document:** Dec 20, 2023
+* **Last change to this document:** Dec 21, 2023
 
 <!--
 * **Reason:**
@@ -249,12 +249,12 @@ A few edge cases after [big keyword argument separation](3.0.html#keyword-argume
 ### Removals[](#removals)
 
 * Constants:
-  * `Fixnum` and `Bignum` (deprecated since unification into `Integer` in [2.4](/2.4.html#fixnum-and-bignum-are-unified-into-integer))
-  * `Random::DEFAULT` (deprecated in favor of per-Ractor random generator since [3.0](/3.0.html#randomdefault-behavior-change))
+  * `Fixnum` and `Bignum` (deprecated since unification into `Integer` in [2.4](2.4.html#fixnum-and-bignum-are-unified-into-integer))
+  * `Random::DEFAULT` (deprecated in favor of per-Ractor random generator since [3.0](3.0.html#randomdefault-behavior-change))
 * Methods:
   * `Dir.exists?`,  `File.exists?` (deprecated since 2.1 as a general rule of having "bare verb" as a method name)
-  * `Object#=~` (deprecated since [2.6](/2.6.html#minor-changes))
-  * `Object#taint`, `#untaint`, `#tainted?`, `#trust`, `#untrust`, `#untrusted?` (deprecated together with a general concept of "safety" since [2.7](/2.7.html#safe-and-taint-concepts-are-deprecated-in-general))
+  * `Object#=~` (deprecated since [2.6](2.6.html#minor-changes))
+  * `Object#taint`, `#untaint`, `#tainted?`, `#trust`, `#untrust`, `#untrusted?` (deprecated together with a general concept of "safety" since [2.7](2.7.html#safe-and-taint-concepts-are-deprecated-in-general))
 
 
 ## Core classes and modules[](#core-classes-and-modules)

3.3.md

@@ -8,9 +8,9 @@ description: Ruby 3.3 full and annotated changelog
 # Ruby 3.3
 
 * **Released at:** Dec 25, 2023 ([NEWS.md](TODO) file)
-* **Status (as of Dec 20, 2023):** TODO
+* **Status (as of Dec 21, 2023):** TODO
 * **This document first published:** Dec 25, 2023
-* **Last change to this document:** Dec 20, 2023
+* **Last change to this document:** Dec 21, 2023
 
 <!--
 * **Reason:**
@@ -22,7 +22,7 @@ description: Ruby 3.3 full and annotated changelog
 
 ## Highlights[](#highlights)
 
-> 3.3 has many important _internal_ changes related to performance optimizations, parser, and JIT (which are mostly of scope of what I am able and willing to cover), but somewhat lighter on the "small quality of life improvement" side.
+> 3.3 has many important _internal_ changes related to performance optimizations, parser, and JIT (which are mostly of scope of what I am able and willing to cover), but somewhat lighter on the "small quality of life improvement" side. See also big [FastRuby's post](https://www.fastruby.io/blog/ruby-3-3.html) mostly focused on the change we do not cover here.
 
 * [`it` will become anonymous block argument in 3.4](#standalone-it-in-blocks-will-become-anonymous-argument-in-ruby-34)
 * [`Module#set_temporary_name`](#moduleset_temporary_name)
@@ -221,7 +221,7 @@ Allows to assign a string to be rendered as class/module's `#name`, without assi
 
 ### `Refinement#refined_class` is renamed to `Refinement#target`[](#refinementrefined_class-is-renamed-to-refinementtarget)
 
-Just a renaming of the unfortunately named new method that [emerged in Ruby 3.2](/rubychanges/3.2.html#refinementrefined_class).
+Just a renaming of the unfortunately named new method that [emerged in Ruby 3.2](3.2.html#refinementrefined_class).
 
 * **Discussion:** [Feature #19714]
 * **Documentation:** <a class="ruby-doc" href="https://docs.ruby-lang.org/en/master/Refinement.html#method-i-target"><code>Refinement#target</code></a>

_data/book.yml

@@ -102,7 +102,7 @@ chapters:
     <p><strong>Highlights:</strong></p>
 
     <blockquote>
-      <p>3.3 has many important <em>internal</em> changes related to performance optimizations, parser, and JIT (which are mostly of scope of what I am able and willing to cover), but somewhat lighter on the “small quality of life improvement” side.</p>
+      <p>3.3 has many important <em>internal</em> changes related to performance optimizations, parser, and JIT (which are mostly of scope of what I am able and willing to cover), but somewhat lighter on the “small quality of life improvement” side. See also big FastRuby’s post mostly focused on the change we do not cover here.</p>
     </blockquote>
 
     <ul>

_src/2.4.md

@@ -189,6 +189,7 @@ New single-method module was introduced, meant to be overridden in order to cont
     ```
   * In Ruby 2.7, new methods [were added](2.7.html#warning-and-) to `Warning` module allowing control over per-category warning suppression;
   * In Ruby 3.0, category support [was improved](3.0.html#warningwarn-category-keyword-argument).
+  * [3.3](3.3.html#new-warning-category-performance): added new warning category: `:performance`.
 
 ### `Object#clone(freeze: false)`
 

_src/2.7.md

@@ -121,7 +121,9 @@ In block without explicitly specified parameters, variables `_1` through `_9` ca
   # %w[test me].each { _1.each_char { p _1 } }
   #                    ^~
   ```
-* **Follow-up:** Warning on attempt to assign to numbered parameter [became errors in 3.0](3.0.html#other-changes).
+* **Follow-ups:**
+  * [3.0](3.0.html#other-changes): Warning on attempt to assign to numbered parameter became errors.
+  * [3.3](3.3.html#standalone-it-in-blocks-will-become-anonymous-argument-in-ruby-34): a warning introduced indicating that in Ruby 3.4, `it` would become an alternative anonymous block parameter (only one, same as `_1`). There is no plan to deprecate numbered parameters.
 
 ### Beginless range
 
@@ -799,6 +801,7 @@ Like `Array#union` and `#difference`, [added](2.6.html#arrayunion-and-arraydiffe
   map[1]
   # => nil  -- value successfully collected, even if key was not GC-able
   ```
+* **Follow-ups:** [3.3](3.3.html#objectspaceweakkeymap): A new class `ObjectSpace::WeakKeyMap` introduced, more suitable for common use-cases of a "weak mapping." It only has garbage-collectable keys.
 
 ### `Fiber#raise`
 
@@ -1028,7 +1031,7 @@ Allows to emit/suppress separate categories of warnings.
   ```
 * **Notes:**
   * The only existing categories currently are `:deprecated` (covers all deprecations) and `:experimental` (as of 2.7, covers only pattern matching)
-  * Note that turning of `:deprecated` warning will also mute the warning of features which was deprecated explicitly in your code, for example with [Module#deprecate_constant](https://ruby-doc.org/core-2.7.0/Module.html#method-i-deprecate_constant)
+  * Note that turning off `:deprecated` warning will also mute the warning of features which was deprecated explicitly in your code, for example with [Module#deprecate_constant](https://ruby-doc.org/core-2.7.0/Module.html#method-i-deprecate_constant)
     ```ruby
     class HTTP
       NOT_FOUND = Exception.new
@@ -1041,7 +1044,9 @@ Allows to emit/suppress separate categories of warnings.
     # ...no warning issued...
     ```
   * Another way to turn on and off separate categories of warnings is passing `-W:(no-)<category>` flag to ruby interpreter, e.g. `-W:no-experimental` means "no warnings when using experimental features".
-* **Follow-up:** In Ruby 3.0, it was [allowed for user code](3.0.html#warningwarn-category-keyword-argument) to specify warning category, and intercept it.
+* **Follow-ups:**
+  * [3.0](3.0.html#warningwarn-category-keyword-argument): user code is allowed to specify warning category, and intercept it;
+  * [3.3](3.3.html#new-warning-category-performance): added new warning category: `:performance`.
 
 ## Standard library
 

_src/3.0.md

@@ -960,6 +960,7 @@ Just fixes an inconsistency introduced by optimization many versions ago.
   processed.lambda? # => false
   processed.call    # => "nil", it is really still not a lambda
   ```
+* **Follow-ups:** [3.3](3.3.html#kernellambda-raises-when-passed-proc-instance): The warning was turned into an exception.
 
 #### `Proc#==` and `#eql?`
 

_src/3.2.md

@@ -249,12 +249,12 @@ A few edge cases after [big keyword argument separation](3.0.html#keyword-argume
 ### Removals
 
 * Constants:
-  * `Fixnum` and `Bignum` (deprecated since unification into `Integer` in [2.4](/2.4.html#fixnum-and-bignum-are-unified-into-integer))
-  * `Random::DEFAULT` (deprecated in favor of per-Ractor random generator since [3.0](/3.0.html#randomdefault-behavior-change))
+  * `Fixnum` and `Bignum` (deprecated since unification into `Integer` in [2.4](2.4.html#fixnum-and-bignum-are-unified-into-integer))
+  * `Random::DEFAULT` (deprecated in favor of per-Ractor random generator since [3.0](3.0.html#randomdefault-behavior-change))
 * Methods:
   * `Dir.exists?`,  `File.exists?` (deprecated since 2.1 as a general rule of having "bare verb" as a method name)
-  * `Object#=~` (deprecated since [2.6](/2.6.html#minor-changes))
-  * `Object#taint`, `#untaint`, `#tainted?`, `#trust`, `#untrust`, `#untrusted?` (deprecated together with a general concept of "safety" since [2.7](/2.7.html#safe-and-taint-concepts-are-deprecated-in-general))
+  * `Object#=~` (deprecated since [2.6](2.6.html#minor-changes))
+  * `Object#taint`, `#untaint`, `#tainted?`, `#trust`, `#untrust`, `#untrusted?` (deprecated together with a general concept of "safety" since [2.7](2.7.html#safe-and-taint-concepts-are-deprecated-in-general))
 
 
 ## Core classes and modules