[#103241] [Ruby master Bug#17777] 2.6.7 fails to build on macOS: implicit declaration of function 'rb_native_mutex_destroy' is invalid in C99 — eregontp@...
Issue #17777 has been reported by Eregon (Benoit Daloze).
17 messages
2021/04/05
[#103305] [Ruby master Feature#17785] Allow named parameters to be keywords — marcandre-ruby-core@...
Issue #17785 has been reported by marcandre (Marc-Andre Lafortune).
21 messages
2021/04/08
[#103342] [Ruby master Feature#17790] Have a way to clear a String without resetting its capacity — jean.boussier@...
Issue #17790 has been reported by byroot (Jean Boussier).
14 messages
2021/04/09
[#103388] [ANN] Multi-factor Authentication of bugs.ruby-lang.org — SHIBATA Hiroshi <hsbt@...>
Hello,
5 messages
2021/04/12
[#103414] Re: [ANN] Multi-factor Authentication of bugs.ruby-lang.org
— Martin J. Dürst <duerst@...>
2021/04/13
Is there a way to use this multi-factor authentication for (like me)
[#103547] List of CI sites to check — Martin J. Dürst <duerst@...>
Hello everybody,
4 messages
2021/04/22
[#103596] [Ruby master Feature#17830] Add Integer#previous and Integer#prev — rafasoaresms@...
Issue #17830 has been reported by rafasoares (Rafael Soares).
9 messages
2021/04/26
[ruby-core:103199] Re: [Ruby master Feature#5446] at_fork callback API
From:
Eric Wong <normalperson@...>
Date:
2021-04-04 05:34:41 UTC
List:
ruby-core #103199
jean.boussier@gmail.com wrote: > Feature #5446: at_fork callback API > https://bugs.ruby-lang.org/issues/5446#change-91273 > > But in practice many libraries prefer to check `Process.pid`, > and often end up doing so in tight loops. And they do it so > much that it end up being significant on performance profiles > in real production environments. Some things have changed in over the years: * getpid() no longer cached by glibc, so it's always a syscall, now * syscalls are more expensive due to CPU vulnerability mitigations * Ractor becoming usable/available in Ruby 3+ * system/popen/backtick use vfork() since Ruby 2.2 * JIT exists: Is there a way to expose Ruby methods/procs as C function pointers with JIT? If so, Fiddle may be usable to call pthread_atfork(3) and have it use JIT-exposed C function pointers. That would be generally useful for interacting with other C libraries, not just for pthread_atfork. Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>