jeremyevans0 (Jeremy Evans)
- Login: jeremyevans0
- Email: merch-redmine@jeremyevans.net
- Registered on: 08/04/2010
- Last sign in: 02/05/2025
Issues
open | closed | Total | |
---|---|---|---|
Assigned issues | 1 | 41 | 42 |
Reported issues | 4 | 144 | 148 |
Projects
Project | Roles | Registered on |
---|---|---|
Ruby | Committer | 04/14/2016 |
Activity
08/01/2025
-
03:22 PM Ruby Bug #21525 (Closed): Inconsistent execution order for methods with constant blocks
-
12:30 AM Ruby Bug #21525: Inconsistent execution order for methods with constant blocks
- Avoiding allocation is deliberate trade-off for these cases, and not the only case where Ruby does this. There are ot...
07/28/2025
-
08:21 PM Ruby Bug #21139: Prism and parse.y parses `it = it` differently
- vinistock (Vinicius Stock) wrote in #note-18:
> Thanks for the context, I understand your point about consistency. S... -
06:07 PM Ruby Bug #21139: Prism and parse.y parses `it = it` differently
- [deleted, duplicate]
-
06:06 PM Ruby Bug #21139: Prism and parse.y parses `it = it` differently
- vinistock (Vinicius Stock) wrote in #note-15:
> The way I reason about this code is as follows:
>
> ```ruby
> 42.tap...
07/20/2025
-
04:29 PM Ruby Feature #21515: Add `&return` as sugar for `x=my_calculation; return x if x`
- lpogic (Łukasz Pomietło) wrote in #note-5:
> The advantage of the proposed syntax is that it does not require an exp...
07/11/2025
-
06:26 AM Ruby Feature #21459 (Closed): Add Set C-API
- Feature added in commit:2ab38691a2683c992bf2886159094afd5e461233
07/09/2025
-
06:35 AM Ruby Bug #21396: Set#initialize should call Set#add on items passed in
- knu (Akinori MUSHA) wrote in #note-10:
> Jeremy, thanks for the reply.
>
> Your point about thread-safety is well... -
12:41 AM Ruby Bug #21396: Set#initialize should call Set#add on items passed in
- knu (Akinori MUSHA) wrote in #note-8:
> Considering the feedback we've received about compatibility in the new exper...
07/06/2025
-
05:19 PM Ruby Bug #21502 (Closed): Segfault with 3.2.8 with frida gem
- Reading https://github.com/hakivvi/frida-ruby/issues/2#issuecomment-3042173245, it looks like it was a bug in the gem...