Xavier Noria

@adrianna-chang-shopify I guess the name "structured event" does not help, because it all seems like a pub/sub system until you arrive to the name `emit`. When I looked into it...

Hey! Quick reply. At first sight it sounds related to autoloading/reloading, but it is interesting that the exception is a bare `NameError`. That means the autoloader is not managing that...

@nativestranger blind shot: is it the case that every time this happens there has been an edit? that is, is the app always reloading?

@headius blind shot: starting with version 2.7.0, explicit namespaces are implemented using the `const_added` hook that was added to Ruby 3.2 (see [this file](https://github.com/fxn/zeitwerk/blob/main/lib/zeitwerk/core_ext/module.rb)). Basically, when the explicit namespace `Hotel`...

@headius hey! Cool, Zeitwerk is pretty stable in general. I believe that if you get `const_added` polished, the suite is going to look much better. The previous technique for explicit...

@rsim fantastic!

Hi @headius! Excellent reduction. With that, I could reproduce without Zeitwerk. Essentially, this is what is happening: ```ruby File.write('bar.rb', 'raise') require './bar' rescue nil File.write('bar.rb', 'Bar = 1') autoload :Bar,...

@headius then why does this work? ```ruby File.write('bar.rb', 'raise') require './bar' rescue nil File.write('bar.rb', 'p 1') require './bar' ``` It prints 1 in both interpreters. Wouldn't the second `require` be...

Regarding the loaders, let me give you folks some context. Being transparent is a design principle of Zeitwerk. The users of your gem do not need to know you are...