Advent of Changelog: Day 20

Author: zverok

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 18, 2023):** 3.2.2 is current _stable_
+* **Status (as of Dec 20, 2023):** 3.2.2 is current _stable_
 * **This document first published:** Feb 4, 2022
-* **Last change to this document:** Dec 18, 2023
+* **Last change to this document:** Dec 20, 2023
 
 <!--
 * **Reason:**
@@ -504,20 +504,7 @@ Returns list of refinements the module defines.
 * **Discussion:** <a class="tracker feature" href="https://bugs.ruby-lang.org/issues/12737">Feature #12737</a>
 * **Documentation:** <a class="ruby-doc" href="https://docs.ruby-lang.org/en/3.2/Refinement.html#method-i-refined_class"><code>Refinement#refined_class</code></a>
 * **Code:** See example above that demonstrates usage of `#refined_class` together with `Module#refinements`.
-* **Note:** The name of the method implies only classes can be refined, which is not true; modules can be refined also, and `refined_class` will promptly return them:
-  ```ruby
-  module BetterEnum
-    refine Enumerable do
-      def each2(&block) = each_slice(2, &block)
-    end
-  end
-
-  BetterEnum.refinements[0].refined_class #=> Enumerable
-
-  using BetterEnum
-  (1..6).each2.to_a #=> [[1, 2], [3, 4], [5, 6]]
-  ```
-  Currently [discussed](https://bugs.ruby-lang.org/issues/19366).
+* **Follow-ups:** [3.3](3.3.html#refinementrefined_class-is-renamed-to-refinementtarget): Renamed to `#target`, because not only classes can be refined, modules too.
 
 #### `Module.used_refinements`[](#moduleused_refinements)
 
@@ -622,7 +609,9 @@ Several method were added that operate on multibyte strings at byte-offset level
   str.byteslice(1..3) #=> "\xB2і" -- works, even if the slice is mid-character
   str.bytesplice(1..3, '...') # offset 1 does not land on character boundary (IndexError)
   ```
-* **Note:** After 3.2 release, `bytesplice` behavior [had changed](https://bugs.ruby-lang.org/issues/19314#note-8) to return `self` instead of replacement string.
+* **Note:**
+  * After 3.2 release, `bytesplice` behavior [had changed](https://bugs.ruby-lang.org/issues/19314#note-8) to return `self` instead of replacement string.
+  * [3.3](3.3.html#stringbytesplice-new-arguments-to-select-a-portion-of-the-replacement-string): parameters added to `bytesplice` to allow partial copy of the buffer.
 
 #### `String#dedup` as an alias for `-"string"`[](#stringdedup-as-an-alias-for--string)
 
@@ -753,6 +742,7 @@ The new protocol for `Time.new` is introduced, that parses Time from string.
   #=> 2023-01-29 00:00:00 +0200
   ```
   * `Time.new('2023')` works, too, but it is a feature that worked before (force-conversion of singular year argument to integer), see <a class="tracker bug" href="https://bugs.ruby-lang.org/issues/19293">Bug #19293</a>. It will probably be deprecated, but can't be quickly removed due to backward compatibility.
+* **Follow-ups:**: [3.3](3.3.html#timenew-with-string-argument-became-stricter): `Time.new` became stricting, accepting only fully-specified date-time.
 
 ### `Struct` and `Data`[](#struct-and-data)
 
@@ -891,7 +881,8 @@ A new class for containing value objects: it is somewhat similar to `Struct` (an
     res
     #=> #<data Result array=[4, 3, 2, 1]>
     ```
-  * `#with` method in Ruby 3.2 is naive and just copies all old and new attributes to the new instance, without invoking any custom initialization methods. In the next version, though, it [expected to call `#initialize`](https://bugs.ruby-lang.org/issues/19259):
+* **Follow-ups:**
+  * `#with` method in Ruby 3.2.0 was naive and just copies all old and new attributes to the new instance, without invoking any custom initialization methods. It was fixed to [call `#initialize`](https://bugs.ruby-lang.org/issues/19259) in 3.2.2:
     ```ruby
     Point = Data.define(:x, :y) do
       def initialize(x:, y:) = super(x: x.to_i, y: y.to_i)
@@ -1128,7 +1119,7 @@ Previously a part of standard library, Set (a collection of unique elements) was
     t.dup.tag #=> nil
     ```
   This is a [bug](https://bugs.ruby-lang.org/issues/19362).
-* **Follow-ups:** [Since Ruby 3.3](3.3.html#procdup-and-clone-call-initialize_dup-and-initialize_copy), `#dup` properly invokes `#initialize_dup`
+* **Follow-ups:** [3.3](3.3.html#procdup-and-clone-call-initialize_dup-and-initialize_copy): `#dup` properly invokes `#initialize_dup`.
 
 #### `Proc#parameters`: new keyword argument `lambda: true/false`[](#procparameters-new-keyword-argument-lambda-truefalse)
 
@@ -1163,7 +1154,7 @@ Previously a part of standard library, Set (a collection of unique elements) was
 
 #### `Method#public?`, `#protected?`, and `#private?` are removed[](#methodpublic-protected-and-private-are-removed)
 
-Predicates to check method visibility added in Ruby 3.1 were reverted.
+Predicates to check method visibility [added in Ruby 3.1](3.1.html#methodunboundmethod-public-private-protected) were reverted.
 
 * **Reason:** The new feature implementation have led to several bugs with `Method` class behavior; while investigating the root cause for those bugs, Matz have decided that method's visibility is not its inherent property, but rather a property of the module/object that owns the method, and as such, is already present in form of `Module#{private,public,protected}_instance_methods` and `Object#{private,public,protected}_methods`
 * **Discussion:** <a class="tracker feature" href="https://bugs.ruby-lang.org/issues/11689#note-24#note-24">Feature #11689<small>#note-24</small></a>

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 19, 2023):** TODO
+* **Status (as of Dec 20, 2023):** TODO
 * **This document first published:** Dec 25, 2023
-* **Last change to this document:** Dec 19, 2023
+* **Last change to this document:** Dec 20, 2023
 
 <!--
 * **Reason:**
@@ -24,11 +24,11 @@ description: Ruby 3.3 full and annotated changelog
 
 > 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.
 
-* [`it` will become anonymous block argument in 3.4]()
-* [`Module#set_temporary_name`]()
-* [`ObjectSpace::WeakKeyMap`]()
-* [`Range#overlap?`]()
-* [`Fiber#kill`]()
+* [`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)
+* [`ObjectSpace::WeakKeyMap`](#objectspaceweakkeymap)
+* [`Range#overlap?`](#overlap)
+* [`Fiber#kill`](#fiberkill)
 
 ## Language changes[](#language-changes)
 
@@ -295,6 +295,32 @@ The low-level string manipulation method now allows to provide a coordinates of
   ```
 * **Notes:** While `symbolize_names:` might looks somewhat strange (usually we talk about hash _keys_), it is done for consistency with Ruby standard library's <a class="ruby-doc" href="https://docs.ruby-lang.org/en/master/JSON.html#module-JSON-label-Output+Options"><code>`JSON.parse`</code></a> signature, which inherited the terminology from the JSON specification.
 
+### `Time.new` with string argument became stricter[](#timenew-with-string-argument-became-stricter)
+
+The method now requires fully-specified date-time string.
+
+* **Discussion:** [Bug #19293]
+* **Documentation:** <a class="ruby-doc" href="https://docs.ruby-lang.org/en/master/Time.html#method-c-new"><code>Time#new</code></a>
+* **Code:**
+  ```ruby
+  Time.new('2023-12-20')
+  # Ruby 3.2: #=> 2023-12-20 00:00:00 +0200
+  # Ruby 3.3: in `initialize': no time information (ArgumentError)
+
+  Time.new('2023-12')
+  # Ruby 3.2: #=> 2023-12-01 00:00:00 +0200
+  # Ruby 3.3: in `initialize': no time information (ArgumentError)
+
+  # Singular year is still works:
+  Time.new('2023')
+  #=> 2023-01-01 00:00:00 +0200
+
+  # ...because it is documented behavior of Time.new to accept
+  # strings that are numeric and treat them as numbers:
+  Time.new('2023', '12', '20')
+  #=> 2023-12-20 00:00:00 +0200
+  ```
+
 ### `Array#pack` and `String#unpack`: raise `ArgumentError` for unknown directives[](#arraypack-and-stringunpack-raise-argumenterror-for-unknown-directives)
 
 * **Discussion:** [Bug #19150]
@@ -519,7 +545,7 @@ Two methods to accept an integer file descriptor as an argument: `for_fd` create
   ```
 * **Notes:**
   * The functionality is only supported on POSIX platforms;
-  * The initial [ticket](https://bugs.ruby-lang.org/issues/19347) only proposed to find a way to be able to change a current directory to one specified by a descriptor (i.e., what eventually became `.fchdir`), but during the discussion a need were discovered for a generic instantiation of a `Dir` instance from the descriptor (what became `from_fd`), as well as a generic way to change the current directory to one specified by `Dir` instance ([`#chdir`](TODO), which is not related to descriptors but is generically useful).
+  * The initial [ticket](https://bugs.ruby-lang.org/issues/19347) only proposed to find a way to be able to change a current directory to one specified by a descriptor (i.e., what eventually became `.fchdir`), but during the discussion a need were discovered for a generic instantiation of a `Dir` instance from the descriptor (what became `from_fd`), as well as a generic way to change the current directory to one specified by `Dir` instance ([`#chdir`](#dirchdir), which is not related to descriptors but is generically useful).
 
 #### `Dir#chdir`[](#dirchdir)
 
@@ -574,6 +600,27 @@ An instance method version of <a class="ruby-doc" href="https://docs.ruby-lang.o
     ```
   * As the impact of the change might be big, note that target version for removal is set to **4.0**. To the best of my knowledge, there are no set date for major version yet.
 
+### `NoMethodError`: change of rendering logic[](#nomethoderror-change-of-rendering-logic)
+
+`NoMethodError` doesn't use target object's `#inspect` in its message, and renders "instance of ClassName" instead.
+
+* **Reason:** While the `#inspect` of the object which failed to respond might be convenient in the error's output, it also might be extremely inefficient and confusing when the object is large and doesn't have `#inspect` redefined to something sensible. It is impossible to require all user objects to redefine `#inspect`, and even if it is redefined, it might be short yet inefficient; so the lesser of evils was chosen and exception's message became more efficient even if less informative.
+* **Documentation:** <a class="ruby-doc" href="https://docs.ruby-lang.org/en/master/NoMethodError.html"><code>NoMethodError</code></a>
+* **Code:**
+  ```ruby
+  "hello".to_ary
+  # Ruby 3.2: undefined method `to_ary' for "hello":String (NoMethodError)
+  # Ruby 3.3: undefined method `to_ary' for an instance of String (NoMethodError)
+
+  # But also, for some complicated data structure:
+  ([{name: 'User 1', role: 'admin'}] * 100).to_josn # typo
+  # Ruby 3.2: undefined method `to_josn' for [{:name=>"User 1", :role=>"admin"}, {:name=>"User 1", :role=>"admin"}, ...
+  # ....10 lines of console output....
+  # ..., {:name=>"User 1", :role=>"admin"}]:Array (NoMethodError)
+  #
+  # Ruby 3.3: undefined method `to_josn' for an instance of Array (NoMethodError)
+  ```
+
 ### `Fiber#kill`[](#fiberkill)
 
 Terminates the Fiber by sending an exception inside it.
@@ -869,22 +916,22 @@ A few changes to mention, though:
 
 _This means that if your dependencies are managed by Bundler and your code depend on `racc`, it should be added to a `Gemfile`._
 
-* racc 1.7.3
+* <a class="github" href="https://github.com/ruby/racc">racc</a> 1.7.3
 
 #### Gems that are warned to become bundled in the next version[](#gems-that-are-warned-to-become-bundled-in-the-next-version)
 
 These gems wouldn't in a Bundler-managed environment unless explicitly added to `Gemfile` since the next version of Ruby. For now, requiring them in such environment would produce a warning. Discussion: [Feature #19351] (initial proposal to promote many gems, which then was deemed problematic), [Feature #19776] (the warning proposal)
 
-* abbrev
-* base64
-* bigdecimal
-* csv
-* drb
-* getoptlong
-* mutex_m
-* nkf
-* observer
-* racc
-* resolv-replace
-* rinda
-* syslog
+* <a class="github" href="https://github.com/ruby/abbrev">abbrev</a>
+* <a class="github" href="https://github.com/ruby/base64">base64</a>
+* <a class="github" href="https://github.com/ruby/bigdecimal">bigdecimal</a>
+* <a class="github" href="https://github.com/ruby/csv">csv</a>
+* <a class="github" href="https://github.com/ruby/drb">drb</a>
+* <a class="github" href="https://github.com/ruby/getoptlong">getoptlong</a>
+* <a class="github" href="https://github.com/ruby/mutex_m">mutex_m</a>
+* <a class="github" href="https://github.com/ruby/nkf">nkf</a>
+* <a class="github" href="https://github.com/ruby/observer">observer</a>
+* <a class="github" href="https://github.com/ruby/racc">racc</a>
+* <a class="github" href="https://github.com/ruby/resolv-replace">resolv-replace</a>
+* <a class="github" href="https://github.com/ruby/rinda">rinda</a>
+* <a class="github" href="https://github.com/ruby/syslog">syslog</a>

_data/book.yml

@@ -106,11 +106,11 @@ chapters:
     </blockquote>
 
     <ul>
-      <li><a href=""><code>it</code> will become anonymous block argument in 3.4</a></li>
-      <li><a href=""><code>Module#set_temporary_name</code></a></li>
-      <li><a href=""><code>ObjectSpace::WeakKeyMap</code></a></li>
-      <li><a href=""><code>Range#overlap?</code></a></li>
-      <li><a href=""><code>Fiber#kill</code></a></li>
+      <li><code>it</code> will become anonymous block argument in 3.4</li>
+      <li><code>Module#set_temporary_name</code></li>
+      <li><code>ObjectSpace::WeakKeyMap</code></li>
+      <li><code>Range#overlap?</code></li>
+      <li><code>Fiber#kill</code></li>
     </ul>
 
     <p><a href="https://rubyreferences.github.io/rubychanges/3.3.html">Read more »</a></p>
@@ -144,6 +144,8 @@ chapters:
       - title: "<code>MatchData#named_captures</code>: <code>symbolize_names:</code>
           argument"
         path: "/3.3.html#matchdatanamed_captures-symbolize_names-argument"
+    - title: "<code>Time.new</code> with string argument became stricter"
+      path: "/3.3.html#timenew-with-string-argument-became-stricter"
     - title: "<code>Array#pack</code> and <code>String#unpack</code>: raise <code>ArgumentError</code>
         for unknown directives"
       path: "/3.3.html#arraypack-and-stringunpack-raise-argumenterror-for-unknown-directives"
@@ -173,6 +175,8 @@ chapters:
         path: "/3.3.html#dirchdir"
       - title: Deprecate subprocess creation with method dedicated to files
         path: "/3.3.html#deprecate-subprocess-creation-with-method-dedicated-to-files"
+    - title: "<code>NoMethodError</code>: change of rendering logic"
+      path: "/3.3.html#nomethoderror-change-of-rendering-logic"
     - title: "<code>Fiber#kill</code>"
       path: "/3.3.html#fiberkill"
     - title: Internals

_src/3.2.md

@@ -504,20 +504,7 @@ Returns list of refinements the module defines.
 * **Discussion:** [Feature #12737](https://bugs.ruby-lang.org/issues/12737)
 * **Documentation:** [Refinement#refined_class](https://docs.ruby-lang.org/en/3.2/Refinement.html#method-i-refined_class)
 * **Code:** See example above that demonstrates usage of `#refined_class` together with `Module#refinements`.
-* **Note:** The name of the method implies only classes can be refined, which is not true; modules can be refined also, and `refined_class` will promptly return them:
-  ```ruby
-  module BetterEnum
-    refine Enumerable do
-      def each2(&block) = each_slice(2, &block)
-    end
-  end
-
-  BetterEnum.refinements[0].refined_class #=> Enumerable
-
-  using BetterEnum
-  (1..6).each2.to_a #=> [[1, 2], [3, 4], [5, 6]]
-  ```
-  Currently [discussed](https://bugs.ruby-lang.org/issues/19366).
+* **Follow-ups:** [3.3](3.3.html#refinementrefined_class-is-renamed-to-refinementtarget): Renamed to `#target`, because not only classes can be refined, modules too.
 
 #### `Module.used_refinements`
 
@@ -622,7 +609,9 @@ Several method were added that operate on multibyte strings at byte-offset level
   str.byteslice(1..3) #=> "\xB2і" -- works, even if the slice is mid-character
   str.bytesplice(1..3, '...') # offset 1 does not land on character boundary (IndexError)
   ```
-* **Note:** After 3.2 release, `bytesplice` behavior [had changed](https://bugs.ruby-lang.org/issues/19314#note-8) to return `self` instead of replacement string.
+* **Note:**
+  * After 3.2 release, `bytesplice` behavior [had changed](https://bugs.ruby-lang.org/issues/19314#note-8) to return `self` instead of replacement string.
+  * [3.3](3.3.html#stringbytesplice-new-arguments-to-select-a-portion-of-the-replacement-string): parameters added to `bytesplice` to allow partial copy of the buffer.
 
 #### `String#dedup` as an alias for `-"string"`
 
@@ -753,6 +742,7 @@ The new protocol for `Time.new` is introduced, that parses Time from string.
   #=> 2023-01-29 00:00:00 +0200
   ```
   * `Time.new('2023')` works, too, but it is a feature that worked before (force-conversion of singular year argument to integer), see [Bug #19293](https://bugs.ruby-lang.org/issues/19293). It will probably be deprecated, but can't be quickly removed due to backward compatibility.
+* **Follow-ups:**: [3.3](3.3.html#timenew-with-string-argument-became-stricter): `Time.new` became stricting, accepting only fully-specified date-time.
 
 ### `Struct` and `Data`
 
@@ -891,7 +881,8 @@ A new class for containing value objects: it is somewhat similar to `Struct` (an
     res
     #=> #<data Result array=[4, 3, 2, 1]>
     ```
-  * `#with` method in Ruby 3.2 is naive and just copies all old and new attributes to the new instance, without invoking any custom initialization methods. In the next version, though, it [expected to call `#initialize`](https://bugs.ruby-lang.org/issues/19259):
+* **Follow-ups:**
+  * `#with` method in Ruby 3.2.0 was naive and just copies all old and new attributes to the new instance, without invoking any custom initialization methods. It was fixed to [call `#initialize`](https://bugs.ruby-lang.org/issues/19259) in 3.2.2:
     ```ruby
     Point = Data.define(:x, :y) do
       def initialize(x:, y:) = super(x: x.to_i, y: y.to_i)
@@ -1128,7 +1119,7 @@ Previously a part of standard library, Set (a collection of unique elements) was
     t.dup.tag #=> nil
     ```
   This is a [bug](https://bugs.ruby-lang.org/issues/19362).
-* **Follow-ups:** [Since Ruby 3.3](3.3.html#procdup-and-clone-call-initialize_dup-and-initialize_copy), `#dup` properly invokes `#initialize_dup`
+* **Follow-ups:** [3.3](3.3.html#procdup-and-clone-call-initialize_dup-and-initialize_copy): `#dup` properly invokes `#initialize_dup`.
 
 #### `Proc#parameters`: new keyword argument `lambda: true/false`
 
@@ -1163,7 +1154,7 @@ Previously a part of standard library, Set (a collection of unique elements) was
 
 #### `Method#public?`, `#protected?`, and `#private?` are removed
 
-Predicates to check method visibility added in Ruby 3.1 were reverted.
+Predicates to check method visibility [added in Ruby 3.1](3.1.html#methodunboundmethod-public-private-protected) were reverted.
 
 * **Reason:** The new feature implementation have led to several bugs with `Method` class behavior; while investigating the root cause for those bugs, Matz have decided that method's visibility is not its inherent property, but rather a property of the module/object that owns the method, and as such, is already present in form of `Module#{private,public,protected}_instance_methods` and `Object#{private,public,protected}_methods`
 * **Discussion:** [Feature #11689#note-24](https://bugs.ruby-lang.org/issues/11689#note-24)