Issue #21272 has been updated by cfis (Charlie Savage). @Eregon - Ah, you are right. Thanks for the pointers to the other issues. Reading them I can see that Class.new is eliminated but I also see this note:
Before inlining, ObjectSpace would report the allocation class path and method id as Class#new which isn't very helpful. With the inlining patch, we can see that the object is allocated in Foo#test.
It seems like tracepoint doesn't report anything anymore though? Should I move my questions to those tickets? Thanks! ---------------------------------------- Feature #21272: Class.new doesn't trigger :class TracePoint https://bugs.ruby-lang.org/issues/21272#change-116320 * Author: st0012 (Stan Lo) * Status: Open ---------------------------------------- According to the official [documentation](https://docs.ruby-lang.org/en/master/TracePoint.html#class-TracePoint-label-...):
To filter what is traced, you can pass any of the following as events:
:class Start a class or module definition.
I'd expect `:class` events to be triggered when new classes are defined via `Class.new` as well, but currently that's not the case. Should we either support `Class.new`, or clarify the behaviour in documentation? ### Reproduction ```rb TracePoint.trace(:class) do |tp| puts "Class created at line: #{tp.lineno}" end class Foo; end # Triggers the tracepoint Baz = Class.new # Doesn't trigger the tracepoint # ruby test.rb # Class created at line: 5 ``` -- https://bugs.ruby-lang.org/