protobuf

Commit Graph

Author	SHA1	Message	Date
Adam Cozzette	ac6852b4a0	Rust: set `ignore` on code example in comment I found that `cargo test` fails without this, because even with `no_run`, Cargo will still try to compile the code. It would be nice to have a working example here, but unfortunately it's non-trivial to set that up since we would need a real generated proto. I also tweaked cargo_test.sh to run the doc tests so that we have CI coverage for those. PiperOrigin-RevId: 703611549	3 months ago
Adam Cozzette	a59bb5ea7f	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	3 months ago
Protobuf Team Bot	671ae8f754	Make protobuf_example publishable by having it only perform code generation behind a feature. PiperOrigin-RevId: 703150378	3 months ago
Adam Cozzette	c18384c40b	Rust: make generated code refer to `::protobuf` instead of `::__pb` This required a tweak to the Bazel aspect to make it alias the appropriate runtime (C++ or upb) under the name `protobuf`. The nice thing about this is that it allows the same generated code to work with both Bazel and Cargo. With Bazel the runtime crate is named `protobuf_cpp` or `protobuf_upb`, whereas with the Cargo build it is just `protobuf`. PiperOrigin-RevId: 703143472	3 months ago
Protobuf Team Bot	ab3adc2da9	Add description and license to protobuf_example's Cargo.toml PiperOrigin-RevId: 702880374	3 months ago
Adam Cozzette	6a0ff9d203	Rust: remove extern crate declaration for `std` from generated code Starting from the 2018 edition of Rust, paths starting with `::` must refer to a crate, so when we refer to `::std` there is no risk of accidental collision with another identifier. Using `::std` instead of `::__std` is useful because it works even when the generated code is in a module rather than directly in the crate root. This allows us to remove one of the post-processing steps from the codegen crate. PiperOrigin-RevId: 702858213	3 months ago
Protobuf Team Bot	2ca39a21d4	Add release.sh script that pushes crates. Temporarily rename the crates `staging-` while we're iterating on this. This works for the protobuf and protobuf_codegen crates, but the protobuf_example crate fails to publish as cargo does not want build.rs to affect files outside of the OUT_DIR. PiperOrigin-RevId: 702840478	3 months ago
Protobuf Team Bot	926f87d7cf	Add publish --dry_run to the cargo_test Add trivial README.md files for this to pass. This will catch some but not all issues with the crates that would cause them to be rejected by crates.io PiperOrigin-RevId: 702766719	3 months ago
Protobuf Team Bot	8e78b9d0c8	Version the protobuf_example crate the same as the other two crates. The Cargo.toml sets both path and version for its dependencies: the mechanism is that path is used if possible (which it is for our test script), but is automatically stripped from the .toml file when uploadeded to Crates.io PiperOrigin-RevId: 702721439	3 months ago
Adam Cozzette	be11a955f1	Rust: delete codegen logic for working with .upb.h files This logic is not necessary anymore now that we are no longer relying on the upb C generated code. PiperOrigin-RevId: 702487648	3 months ago
Protobuf Team Bot	90e57d686f	Add .gitignore to the protobuf_example crate that ignores src/protobuf_generated/ Because we glob */ this will get picked up for the tar just by adding the file. PiperOrigin-RevId: 702470234	3 months ago
Protobuf Team Bot	c531f2a920	Make the default directory for cargo gencode `src/protobuf_generated/` instead of `protos`. PiperOrigin-RevId: 702469285	3 months ago
Protobuf Team Bot	8ce4952624	Create /release_crates/ directory that contains one directory for each of our 3 crates that we package up. PiperOrigin-RevId: 702439996	3 months ago

13 Commits (20ea8af6e7cbda6601e9436e854d690b3a53c46c)