tree eeb3fe64af88ca129252875a7501780e7c41aaa1
parent 276792923cf87d8f976651a00a0983eee03d8b31
author Adam Cozzette <acozzette@google.com> 1733512241 -0800
committer Copybara-Service <copybara-worker@google.com> 1733512421 -0800

Rust: remove references to `crate::` from generated code

This is necessary for the generated code to work correctly even when it's
placed in a module instead of directly in the crate root. Now we can finally
delete the last of the gencode post-processing from the protobuf_gencode crate.

To get this to work properly I had to update the `Context` object to keep track
of the current module depth. This way we know how many `super::` prefixes we
need to prepend to an identifier to get back to the top level.

I had to some refactoring of our naming helper functions to get everything
working properly:
 - Deleted `GetCrateRelativeQualifiedPath()`, since it seems simpler if we just
   always provide unambiguous paths. I added some new `RsTypePath()` overloads
   as a replacement.
 - Made `RustModuleForContainingType()` a private implementation detail of
   naming.cc, since the `RustModule()` functions are more user-friendly and
   accomplish the same thing.
 - Moved the logic for prepending super:: or the foreign crate name into
   `RustModuleForContainingType()`. This way, all the helpers that call that
   function automatically pick up the behavior we want.

PiperOrigin-RevId: 703555727