[#107867] Fwd: [ruby-cvs:91197] 8f59482f5d (master): add some tests for Unicode Version 14.0.0 — Martin J. Dürst <duerst@...>
To everybody taking care of continuous integration:
3 messages
2022/03/13
[#108090] [Ruby master Bug#18666] No rule to make target 'yaml/yaml.h', needed by 'api.o' — duerst <noreply@...>
Issue #18666 has been reported by duerst (Martin D端rst).
7 messages
2022/03/28
[#108117] [Ruby master Feature#18668] Merge `io-nonblock` gems into core — "Eregon (Benoit Daloze)" <noreply@...>
Issue #18668 has been reported by Eregon (Benoit Daloze).
22 messages
2022/03/30
[ruby-core:107972] [Ruby master Feature#18647] Non-recursive option for iseq-targeted Tracepoints in ruby 2.6+
From:
"hurricup (Alexandr Evstigneev)" <noreply@...>
Date:
2022-03-18 09:41:37 UTC
List:
ruby-core #107972
Issue #18647 has been reported by hurricup (Alexandr Evstigneev). ---------------------------------------- Feature #18647: Non-recursive option for iseq-targeted Tracepoints in ruby 2.6+ https://bugs.ruby-lang.org/issues/18647 * Author: hurricup (Alexandr Evstigneev) * Status: Open * Priority: Normal ---------------------------------------- I can see that iseq-targeted TracePoints introduced in ruby 2.6 working recursively and there is no API to avoid that, even on C level, because related method is not exported by rubylib. This may be handy in some cases, but I'd like to be able to put precise tracepoint to the method line (without any child iseqs, like blocks on the same line) Would be really nice to have some `recursive = true` argument in the `enable` method. Otherwise, to implement some precise breakpoint I need manually to check if topmost user iseq is the expected one. This may be really bad for performance in some cases. -- https://bugs.ruby-lang.org/ Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>