[#89555] [Ruby trunk Feature#15251] Hash aset should deduplicate non tainted string — chopraanmol1@...
Issue #15251 has been updated by chopraanmol1 (Anmol Chopra).
3 messages
2018/10/25
[#89583] [PATCH] vm_trace.c (postponed_job_register): only hit main thread — Eric Wong <normalperson@...>
@hsbt: I post here on ruby-core because I hit errors with
5 messages
2018/10/27
[#89584] Re: [PATCH] vm_trace.c (postponed_job_register): only hit main thread
— Koichi Sasada <ko1@...>
2018/10/27
thank you for you patch.
[#89590] Re: [PATCH] vm_trace.c (postponed_job_register): only hit main thread
— Eric Wong <normalperson@...>
2018/10/28
Koichi Sasada <ko1@atdot.net> wrote:
[#89621] [Ruby trunk Bug#14867] Process.wait can wait for MJIT compiler process — Greg.mpls@...
Issue #14867 has been updated by MSP-Greg (Greg L).
4 messages
2018/10/29
[#89622] Re: [Ruby trunk Bug#14867] Process.wait can wait for MJIT compiler process
— Eric Wong <normalperson@...>
2018/10/29
Greg.mpls@gmail.com wrote:
[#89627] [Ruby trunk Bug#14867] Process.wait can wait for MJIT compiler process — takashikkbn@...
Issue #14867 has been updated by k0kubun (Takashi Kokubun).
3 messages
2018/10/30
[#89654] [Ruby trunk Bug#14867] Process.wait can wait for MJIT compiler process — takashikkbn@...
Issue #14867 has been updated by k0kubun (Takashi Kokubun).
4 messages
2018/10/31
[#89655] Re: [Ruby trunk Bug#14867] Process.wait can wait for MJIT compiler process
— Eric Wong <normalperson@...>
2018/10/31
takashikkbn@gmail.com wrote:
[ruby-core:89512] Re: [Ruby trunk Bug#15241] net/pop fix to use mutable strings was too eager
From:
Eric Wong <normalperson@...>
Date:
2018-10-22 18:31:31 UTC
List:
ruby-core #89512
```
me@brian-donovan.com wrote:
> https://bugs.ruby-lang.org/issues/15241
> See
> [[https://github.com/ruby/ruby/commit/3993fbb5f6bfdae0bce040988d7e2dd632247cdc#commitcomment-30987842|this
> thread on Github]]. I believe the changes made in Backport
> #14416 for 2.5.2 (on both trunk and 2.5.x) over-eagerly
> applied mutability to literal strings. In particular, the
> strings returned by `inspect` have no real need to be mutable
> as far as I can tell.
We cannot make assumptions about how people use strings returned
from .inspect. Such code exists and we should not break it:
warn(foo.inspect << " #{__FILE__}:#{__LINE__}")
Disclaimer: I do not speak for the rest of ruby-core.
This worked in 2.2 and earlier, and we should be maintaining
compatibility with such code. If we have .inspect method
returning frozen strings, I consider it a bug.
I hate that we allocate extra objects and lose performance;
but losing compatibility and breaking existing code is worse.
```
Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>