A `def`-ed method of a shareable object may depend on unshareable state. Even worse, shareability of state may dynamically change: ```ruby module Checker CHECK = [] def check? CHECK.include?(self) end end class A; i...trinistr (Alexander Bulancov)
jneen (Jeanine Adkisson) wrote in #note-16: > I wonder if exposing a static `Object.class_of(thing)` would be appropriate? There's also the singleton_class to consider as well. This is an interesting idea. It would solve the problems...trinistr (Alexander Bulancov)
[Doors](https://en.wikipedia.org/wiki/Doors_(computing)) are a thing on Solaris. Event ports are also [reportedly](https://runebook.dev/en/docs/python/library/stat/stat.S_ISPORT) a Solaris thing, but all references seem to be about the P...trinistr (Alexander Bulancov)
`PP` expects that a `#pretty_print` method can be used with both `PrettyPrint` and `PrettyPrint::SingleLine` interchangeably. This is used to [implement](https://github.com/ruby/pp/blob/b6f81ef83f9137c2300cb5eb96d440419c8f886f/lib/pp.rb#...trinistr (Alexander Bulancov)
> Using `/(\p{Word}|\p{S})/` is kind of a workaround, but it is slower. Have you tried a non-capturing group? `/(?:\p{Word}|\p{S})/` should have better performance.trinistr (Alexander Bulancov)
I would like to revive discussion for this feature request as I feel that `BasicObject#__class_` is still needed. Note: obviously, it is possible to transplant methods with `define_method` (that is very nice!), but one doesn't always ...trinistr (Alexander Bulancov)
> Any value that responds to `to_proc` and returns a `Proc` object is accepted in these options. An alternative is using "pattern" values with `#===`, like `Enumerable.grep` does. This would allow using not only Proc objects, but also...trinistr (Alexander Bulancov)
> Percentiles would be nice, especially if there is a more efficient algorithm for them than just sorting + indexing. It may be reasonable to implement percentiles without sorting, expecting the array to be pre-sorted, in the same way...trinistr (Alexander Bulancov)
> Useful context for this issue which would make sense to add the description is this Regexp item from the NEWS of 3.3 Yes, thank you, that's what lead to me making the wrong assumption about linearity of lookbehind. > ... Suprisin...trinistr (Alexander Bulancov)