Advent of Changelog: Day 14

Author: zverok

_src/3.3.md

@@ -286,11 +286,11 @@ A new "weak map" concept implementation. Unlike `ObjectSpace::WeakMap`, it compa
 
 ### `Process.warmup`
 
-* **Reason:**
+A method to call when a long-running application finalized its loading, and before the regular work is started. TODO: forks?
+
 * **Discussion:** [Feature #18885]
 * **Documentation:** [Process.warmup](https://docs.ruby-lang.org/en/master/Process.html#method-c-warmup)
-* **Code:**
-* **Notes:**
+* **Notes:** Hardly something can be explained or showcased here better than the justification discussion linked above and the method docs are doing it.
 
 ### `Process::Status#&`  and `#>>` are deprecated
 
@@ -354,6 +354,8 @@ The low-level string manipulation method now allows to provide a coordinates of
 * **Documentation:** [String#bytesplice](https://docs.ruby-lang.org/en/master/String.html#method-i-bytesplice)
 * **Code:**
   ```ruby
+  # TODO: Write real working code!
+
   # Base usage
   'foo'.byteplice(1..2, 'bar', 0..1)
   # The receiver is modified
@@ -421,8 +423,7 @@ Allows to trace when some exception was `rescue`'d in the code of interest.
   lambda(&:to_s) #=> works
   lambda(&method(:puts)) #=> works
   ```
-* **Notes:**
-  * The discussion was once [started](https://bugs.ruby-lang.org/issues/15973) from the proposal to make `lambda` change "lambiness" of a passed block, but it raises multiple issues (changing the block semantics mid-program is just one of them). In general, `lambda` as a _method_ is considered legacy, inferior to the `-> { }` lambda literal syntax, exactly due to problems like this: it looks like a regular method that receives a block, and therefore should be able accept _any_ block, but in fact it is "special" method. So in 3.0, there was a warning about `lambda(&proc_instance)`, and since 3.3, the warning finally turned into an error.
+* **Notes:** The discussion was once [started](https://bugs.ruby-lang.org/issues/15973) from the proposal to make `lambda` change "lambiness" of a passed block, but it raises multiple issues (changing the block semantics mid-program is just one of them). In general, `lambda` as a _method_ is considered legacy, inferior to the `-> { }` lambda literal syntax, exactly due to problems like this: it looks like a regular method that receives a block, and therefore should be able accept _any_ block, but in fact it is "special" method. So in 3.0, there was a warning about `lambda(&proc_instance)`, and since 3.3, the warning finally turned into an error.
 
 ### Deprecate subprocess creation with method dedicated to files
 
@@ -519,7 +520,7 @@ Terminates the Fiber by sending an exception inside it.
 * **Documentation:** [Fiber#kill](https://docs.ruby-lang.org/en/master/Fiber.html#method-i-kill)
 * **Code:**
   ```ruby
-  TODO: various behaviors
+  # TODO: base behaviors & edge cases!
 
   # Semi-realistic usage example:
   reader = Fiber.new do
@@ -539,14 +540,6 @@ Terminates the Fiber by sending an exception inside it.
   ```
 * **Notes:**
 
-### `Encoding#replicate` is removed
-
-* **Reason:**
-* **Discussion:** [Feature #18949]
-* **Documentation:** —
-* **Code:**
-* **Notes:**
-
 ### `Range#overlap?`
 
 Checks for overlapping of two ranges.