Ruby

As the current behavior of the backtrace, if the receiver class is completely bound to the constant names, they are prefixed to the method names in the backtrace. So, if you do:

NS1 = Namespace.new NS1.load "foo.rb" NS2 = Namespace.new NS2.load "foo.rb" NS1::Foo.test(NS1, NS2, 10) 

you will see:

$ RUBY_NAMESPACE=1 ./miniruby test.rb ./miniruby: warning: Namespace is experimental, and the behavior may change in the future! See doc/namespace.md for know issues, etc. foo.rb:9:in 'NS1::Foo.test' foo.rb:7:in 'NS2::Foo.test' foo.rb:9:in 'NS1::Foo.test' foo.rb:7:in 'NS2::Foo.test' foo.rb:9:in 'NS1::Foo.test' foo.rb:7:in 'NS2::Foo.test' foo.rb:9:in 'NS1::Foo.test' foo.rb:7:in 'NS2::Foo.test' foo.rb:9:in 'NS1::Foo.test' foo.rb:7:in 'NS1::Foo.test' test.rb:23:in '<main>' 

This depends on the output of Class#name, so the result may change depending of the progress of #21316.

It is possible to change how to display the backtrace to show class names that are not completely bound to constants.
I have conservatively designed the current spec of the backtrace to avoid potential confusing output, but I'm not sure which would be better.

diff --git a/vm_backtrace.c b/vm_backtrace.c index 26e0a6fb76..15ec9b7a4d 100644 --- a/vm_backtrace.c +++ b/vm_backtrace.c @@ -201,20 +201,19 @@ VALUE rb_mod_name0(VALUE klass, bool *permanent); VALUE rb_gen_method_name(VALUE owner, VALUE name) { - bool permanent;  if (RB_TYPE_P(owner, T_CLASS) || RB_TYPE_P(owner, T_MODULE)) { if (RCLASS_SINGLETON_P(owner)) { VALUE v = RCLASS_ATTACHED_OBJECT(owner); if (RB_TYPE_P(v, T_CLASS) || RB_TYPE_P(v, T_MODULE)) { - v = rb_mod_name0(v, &permanent); - if (permanent && !NIL_P(v)) { + v = rb_mod_name(v); + if (!NIL_P(v)) {  return rb_sprintf("%"PRIsVALUE".%"PRIsVALUE, v, name); } } } else { - owner = rb_mod_name0(owner, &permanent); - if (permanent && !NIL_P(owner)) { + owner = rb_mod_name(owner); + if (!NIL_P(owner)) {  return rb_sprintf("%"PRIsVALUE"#%"PRIsVALUE, owner, name); } } 

$ RUBY_NAMESPACE=1 ./miniruby test.rb ./miniruby: warning: Namespace is experimental, and the behavior may change in the future! See doc/namespace.md for know issues, etc. foo.rb:9:in '#<Namespace:0x00007ff4d61f9f20>::Foo.test' foo.rb:7:in '#<Namespace:0x00007ff4d61f93e0>::Foo.test' foo.rb:9:in '#<Namespace:0x00007ff4d61f9f20>::Foo.test' foo.rb:7:in '#<Namespace:0x00007ff4d61f93e0>::Foo.test' foo.rb:9:in '#<Namespace:0x00007ff4d61f9f20>::Foo.test' foo.rb:7:in '#<Namespace:0x00007ff4d61f93e0>::Foo.test' foo.rb:9:in '#<Namespace:0x00007ff4d61f9f20>::Foo.test' foo.rb:7:in '#<Namespace:0x00007ff4d61f93e0>::Foo.test' foo.rb:9:in '#<Namespace:0x00007ff4d61f9f20>::Foo.test' foo.rb:7:in '#<Namespace:0x00007ff4d61f9f20>::Foo.test' test.rb:23:in '<main>' 

The ns_id seems good to be shown in backtrace (I'm unsure about this format is good or not):

foo.rb:7:in namespace(1) 'Foo.test' 

mame (Yusuke Endoh) wrote in #note-2:

As the current behavior of the backtrace, if the receiver class is completely bound to the constant names, they are prefixed to the method names in the backtrace.

Ah, ok, I didn't know that. Thank you.

I'm not sure if printing the address or the ns_id is better. Either works for me, but I'm not sure what would be most ergonomic.

mame (Yusuke Endoh) wrote in #note-4:

foo.rb:9:in '#<Namespace:0x00007ff4d61f9f20>::Foo.test' foo.rb:7:in '#<Namespace:0x00007ff4d61f93e0>::Foo.test' 

I took me quite a while to notice that 0x00007ff4d61f9f20 and 0x00007ff4d61f93e0 were different.

Just my personal preference, but if #<Namespace:0x00007ff4d61f93e0> is assigned to constant X I would like to see:

foo.rb:9:in namespace(1) 'Foo.test' foo.rb:7:in namespace(X) 'Foo.test' 

I'd like to keep this issue pending until we provide high level API (maybe Package). See #21385)

Matz.