> ``` > ... For me, ensure => ret looks cleaner, reduces cognitive overhead, and is simply easier on the eyes when reviewing real code. The structure is easier to parse visually, and the intent is clearer compared to the alternativ...artemb (Artem Borodkin)
I'd like to propose a simple feature that allows easy access to the return value inside an ensure block. ```ruby begin # ... ensure => ret # ret is nil if an exception is raised LOGGER.debug "return value: #{ret}" en...artemb (Artem Borodkin)
You’re absolutely right; this part does seem ambiguous. I initially added it as an empty block, modeled after the short syntax, like this: ```ruby def initialize(name, age, email = nil) = (@name, @age, @email = name, age, email) ``` Wh...artemb (Artem Borodkin)
# Constructor Parameter Shortcuts I propose adding a new syntax to simplify the constructor definition in the classes. Defining a constructor often involves repetitive assignments of parameters to instance variables. This pattern is v...artemb (Artem Borodkin)
Eregon (Benoit Daloze) wrote in #note-2: > I think pattern matching should be used here instead Very nice, thank you! If kind_of? (and alias is_a?) has a strong implementation optimization, I agree that this is not so important enhanc...artemb (Artem Borodkin)
I propose allowing multiple arguments to be passed to the .is_a? Method imply "OR" semantics: ``` ruby name.is_a? String, Symbol ``` Currently, we need to write the following to achieve the same functionality: ``` ruby [Str...artemb (Artem Borodkin)
Are there any proposal issues regarding the addition of argument and block support for the ```.each(&:method, args) do; end``` syntax? It seems quite feasible to support it natively. ``` ruby module Enumerable def each_call...artemb (Artem Borodkin)
artemb (Artem Borodkin)08:28 PM Ruby Feature #21822: Expose Return Value in the ensure Block