Actions
Misc #21281
closed
Updated by mame (Yusuke Endoh) 2 months ago
- Related to : [META] DevelopersMeeting added
Updated by byroot (Jean Boussier) 2 months ago · Edited
- [Feature ] Actually deprecate
ObjectSpace._id2ref(byroot)- Matz agreed to deprecate
_id2reffor Ruby 2.7 but that was never implemented. - I have a PR open to finally do it, but should the deprecation mention the removal timeline, is there one?
- The main user is
drbbut there is a PR open to solve it: https://.com/ruby/drb/pull/31
- Matz agreed to deprecate
Updated by tagomoris (Satoshi Tagomori) about 2 months ago · Edited
- [Feature ] Namespace on read (tagomoris)
- I'm finishing the namespace branch to be ready for merge (disabled by default) https://.com/tagomoris/ruby/tree/namespace-on-read-classext
- Current status:
- Default (Namespace disabled, YJIT/ZJIT disabled):
make checkandmake exampassed on my macOS (not checked on CI) - Namespace enabled:
make checkpassed butmake examfailed (the known cause and I'll update the implementation soon)
- Default (Namespace disabled, YJIT/ZJIT disabled):
- I hope it'll be merged without further more rebases :P
Updated by jeremyevans0 (Jeremy Evans) about 2 months ago
- [Feature ] Show performance warnings for easily avoidable unnecessary implicit splat allocations (jeremyevans0)
- This warning only shows method calls that are allocating unnecessarily, where allocation can be avoided by using a local variable.
- This warning found unnecessary allocations in the standard library, rubygems, Rails, and Sequel.
- We are currently only using performance warnings for objects with too many shapes.
- Is this OK to commit?
- [Feature ] Remove SortedSet autoload and set/sorted_set (jeremyevans0)
- Set is now a core class, and the SortedSet autoload that was in set.rb is now in core.
- This autoload only works if the sorted_set gem is installed.
- I don't think we should have this autoload, can we remove it?
- If so, do we want to deprecate the autoload before removing it?
- [Bug ] Remove or Fix Set#to_h (jeremyevans0)
- The method was not present in stdlib Set, and not previously approved for addition.
- However, psych started using it.
- The method is not backwards compatible with the previous Set#to_h (implemented by Enumerable#to_h).
- I recommend we remove it and fix psych, and have a pull request for that.
- If we want to keep it, I have a pull request to fix it, and add tests and documentation.
- Do we want to keep Set#to_h and have a return a true-valued hash if not given a block?
- [Bug ] StringIO#set_encoding warns when backed by chilled string literal (jeremyevans0)
- This warning is bogus, as most code using this does not need changes when string literals are frozen.
- Issuing bogus warnings prompts for unnecessary code changes and should be avoided.
- StringIO#set_encoding already does not set the encoding if the string is frozen, since [Bug ]
- I recommend we stop setting the underlying encoding for non-frozen strings to avoid the warning.
- This could be done for only chilled strings, or for all strings if behavior should be consistent.
- Should we make this change, and if so, for chilled strings or for both chilled and unfrozen strings?
Updated by mame (Yusuke Endoh) about 2 months ago · Edited
- [Feature ] A way to strictly validate time input (mame)
- I want to confirm that the current tolerant behavior of Time.new is intentional, and if so, want a strict variant of Time.new.
Updated by jhawthorn (John Hawthorn) about 2 months ago
- [Feature ]
respond_tocheck inClass#allocateis inconsistentClass#allocatedoes a slowrespond_tocheck to try to prevent uninitialized values viamethod(:allocate).bind_callonMatchData,Refinement,Module,Complex,Rational- The
respond_tocheck is easy to trick and bypass. Even if it was more strict, it does not seem to provide additional safety as there are other ways to construct uninitialized objects. - Is it OK to remove?
Updated by hsbt (Hiroshi SHIBATA) about 2 months ago · Edited
- [Feature ] Retire CGI library from Ruby 3.5
- Can I remove CGI library without
CGI::Util? - What's the preferred migration process?
- We keep only cgi/escape (C impl)feature in Ruby.
- We keep
cgi/utilwithcgi/escape. The current CGI library is removed and depend cgi-util gem. - We migrate cgi/escape to other class/module. The current CGI library and cgi/escape are removed.
- We provide cgi-util gem for migration with deprecated warning at Ruby 3.5. In next year, we will remove cgi-util gem.
- Can I remove CGI library without
Updated by Actions
Like0Like0Like0Like0Like0Like0Like0Like0Like0Like0