Benoit Daloze

The README says: > The design goals of this gem are: > * ... > * Remain free of external gem dependencies So we have no choice but to break...

I cannot reproduce the deadlock with the stdlib logger with 3.3.5. But given how little concurrent-ruby uses logging I think it's best to keep using its simple logger and avoid...

I came up with a PR to remove the dependency on logger: https://github.com/ruby-concurrency/concurrent-ruby/pull/1062

https://github.com/ruby-concurrency/concurrent-ruby/releases/tag/v1.3.5

Thank you for your contribution! This has been merged by @Sowasvonbot in https://github.com/oracle/graalpython/commit/6171b1fa9528559318828ec7b6b731e18581d48d and https://github.com/oracle/graalpython/commit/86885bfc1236f7ae4575f9ed43b60958cc9e9388.

So https://github.com/ruby/setup-ruby/blob/7bae1d00b5db9166f4f0fc47985a3a5702cb58f0/bundler.js#L212 could be a cause of what you see? How would you propose to workaround that, can you make a PR? I wonder if this could be an issue...

FWIW I think cache keys should be case-sensitive, because they might contain paths and such paths are case sensitive and the difference could matter, e.g. `gemfile` vs `Gemfile` on Linux.

The problem is e.g. `rb_nkf_putchar()` is a callback called as `putchar()` from `src/main/c/nkf/nkf-utf8/nkf.c`. So I think it's too messy to pass a struct there. Let's try using `thread_local` (https://en.cppreference.com/w/c/thread/thread_local) or...

:+1: to add BLAKE3 from me. As we have seen in TruffleRuby already some time ago, having a digest implementation as a C API (to be precise, not using Digest's...

> did TruffleRuby end up moving to a `ripper` implementation based on prism No, it didn't, we tried but we found it rather incomplete. It needs changes in Prism. >...