shyouhei (Shyouhei Urabe) wrote in #note-4: > Reminds me of discussions in ISO C/C++ committee (in both, simultaneously, by the same person). C23 opted not to have binary string literal, instead introduced a way to load binaries into C ...ziggythehamster (Keith Gable)
rubyFeedback (robert heiler) wrote in #note-1: > I think it may be easier to focus only on %b() at first, rather than concomitantly on %B() as > ... I agree with that. Technically `%B[]` would be equivalent to `IO::Buffer.for(%b[])` an...ziggythehamster (Keith Gable)
I sometimes find myself needing to write some bytes in a Ruby string literal, and this experience leaves a lot to be desired: * Bare strings don't work (potential for encoding corruption unless you remember to `.force_encoding` and ne...ziggythehamster (Keith Gable)
byroot (Jean Boussier) wrote in #note-1: > Thanks for the report. Editing the issue to mark this commit for backport. > ... This being my first bug - did you mean to make it status Closed?ziggythehamster (Keith Gable)
Ruby 3.2 segfaults reproducibly for us on aarch64 (Graviton2) and x86_64 with YJIT enabled ... however all of my attempts to make a minimal reproducible test case have failed. The control frame of the segfault isn't consistent, but the C...ziggythehamster (Keith Gable)
A sole positional argument does in fact work, and I am a big fan of the pattern matching feature (enough that once we're on 2.7, I'm considering `-W:no-experimental`), but I hadn't thought about the combination of the two, and I certainl...ziggythehamster (Keith Gable)
A use case that seems to have been forgotten that I want to explicitly point out (and I'm not sure if this is the ticket for it, given the discussion here vs. the linked thread, so I'm happy to open a new issue if needed) is that it seem...ziggythehamster (Keith Gable)
ziggythehamster (Keith Gable)02:34 AM Ruby Feature #20196: Proposal: Binary data literal