[#101179] Spectre Mitigations — Amel <amel.smajic@...>
Hi there!
5 messages
2020/12/01
[#101180] Re: Spectre Mitigations
— Chris Seaton <chris@...>
2020/12/01
I wouldn’t recommend using Ruby to run in-process untrusted code in the first place. Are people doing that?
[#101694] Ruby 3.0.0 Released — "NARUSE, Yui" <naruse@...>
We are pleased to announce the release of Ruby 3.0.0. From 2015 we
4 messages
2020/12/25
[ruby-core:101646] [Ruby master Bug#17429] Prohibit include/prepend in refinement modules
From:
eregontp@...
Date:
2020-12-23 11:00:20 UTC
List:
ruby-core #101646
Issue #17429 has been updated by Eregon (Benoit Daloze). +1 from me! I think a new Module method to copy all methods to another Module could be useful. Something like `A.copy_methods(B)`. It seems there is no need to copy constants, because the constant scope of "copied" methods would still be `A` (and lexical parents). Actually the method would only do a shallow copy of each method, i.e., still use the same bytecode, etc, so maybe another name than `copy_methods` would be clearer. The docs of `Module#append_features` make it sounds like `#append_features` would do that, but it doesn't. Actually, #append_features adds the given module in the ancestors chain (include = append_features + included). Would be a good occasion to clarify the docs of `#append_features`. ---------------------------------------- Bug #17429: Prohibit include/prepend in refinement modules https://bugs.ruby-lang.org/issues/17429#change-89436 * Author: shugo (Shugo Maeda) * Status: Open * Priority: Normal * Backport: 2.5: UNKNOWN, 2.6: UNKNOWN, 2.7: UNKNOWN ---------------------------------------- include/prepend in refinement modules has implementation difficulties such as #17007 and #17379, and tends to be misleading like #17374. How about to prohibit it in future versions? Method copy like #17380 may be more convenient, but it's confusing to use names include and prepend because semantics is different from the original ones. -- https://bugs.ruby-lang.org/ Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>