byroot (Jean Boussier)
- Login: byroot
- Email: byroot@ruby-lang.org, jean.boussier+ruby-lang@gmail.com, jean.boussier@shopify.com, jean.boussier@gmail.com
- Registered on: 03/11/2014
- Last sign in: 03/19/2026
Issues
| open | closed | Total | |
|---|---|---|---|
| Assigned issues | 0 | 28 | 28 |
| Reported issues | 28 | 138 | 166 |
Projects
| Project | Roles | Registered on |
|---|---|---|
| Ruby | Committer | 09/27/2021 |
Activity
05/12/2026
-
07:07 AM Ruby Revision 95c041bd (git): [ruby/json] generator.c: Handle stupidly large depth
- https://github.com/ruby/json/commit/1d32bd4596
-
06:25 AM Ruby Revision fb369617 (git): [ruby/json] Add missing write barrier in ParserConfig
- This couldn't possibly lead to a crash unless you'd mess
with GC.stress or `send(:initialize)` on an old object.
But for correctness, it should be there.
https://github.com/ruby/json/commit/ab6972d797
05/11/2026
-
07:08 PM Ruby Feature #13677 (Open): Add more details to error "Name or service not known (SocketError)"
05/10/2026
05/06/2026
-
04:05 PM Ruby Feature #22056: Add zero-copy String constructor backed by an arbitrary Ruby object
- Another though: what does it means for coderanges? Since the buffer is owned by another object, it can be mutated without going through one of String methods, which means things like `ENC_CODERANGE_CLEAR` won't happen.
Perhaps it's ac... -
04:01 PM Ruby Feature #22056: Add zero-copy String constructor backed by an arbitrary Ruby object
- > by leveraging the existing STR_NOFREE mechanism.
I see. So it's mutable, but Copy-on-Write. If you mutate the string, all the content is copied in a buffer managed by Ruby. -
02:13 PM Ruby Feature #22056: Add zero-copy String constructor backed by an arbitrary Ruby object
- Somewhat related proposal: [Feature #20878]
I also wonder, this new "external" string is supposed to be mutable? If so that may increase `string.c` complexity significantly, as all codepaths that normally resize the string buffer will... -
08:10 AM Ruby Revision 4eeec614 (git): shapes: Rename `TOO_COMPLEX` in just `COMPLEX`
- The `too_` prefix wasn't consistently used and just make the
thing longer for no benefit. -
08:10 AM Ruby Revision deceb9f6 (git): Rename `rb_shape_obj_*` into `rb_obj_shape_*`
- For consistency.
-
07:02 AM Ruby Revision 678d86f5 (git): shape.c: transition to complex when `max_capacity` is reached
- Now that we have 1024B slots, we can store up to 126 fields inline.
Objects larger than this are rare if not non-existent, hence we can
get rid of the `malloc` path for imemo/fields and simply transition
to `TOO_COMPLEX`.
This addition...