U:RDoc::AnyMethod[iI"zeitwerk_original_require:ETI"%Kernel#zeitwerk_original_require;TF:publico:RDoc::Markup::Document:@parts[o:RDoc::Markup::Paragraph;	[I"QZeitwerk's main idea is to define autoloads for project constants, and then ;TI"Iintercept them when triggered in this thin `Kernel#require` wrapper.;To:RDoc::Markup::BlankLineo;
;	[I"RThat allows us to complete the circle, invoke callbacks, autovivify modules, ;TI"Qdefine autoloads for just autoloaded namespaces, update internal state, etc.;T@o;
;	[
I"ROn the other hand, if you publish a new version of a gem that is now managed ;TI"Rby Zeitwerk, client code can reference directly your classes and modules and ;TI"Rshould not require anything. But if someone has legacy require calls around, ;TI"Qthey will work as expected, and in a compatible way. This feature is by now ;TI"#EXPERIMENTAL and UNDOCUMENTED.;T@o;
;	[I"MWe cannot decorate with prepend + super because Kernel has already been ;TI"Lincluded in Object, and changes in ancestors don't get propagated into ;TI"4already existing ancestor chains on Ruby < 3.0.;T:
@fileI"lib/zeitwerk/kernel.rb;T:0@omit_headings_from_table_of_contents_below000[I"(path);T@ FI"Kernel;TcRDoc::NormalModule0[@#FI"require;T