cargo-raze
prost
Our great sponsors
cargo-raze | prost | |
---|---|---|
6 | 14 | |
475 | 3,513 | |
0.6% | 4.6% | |
1.7 | 8.3 | |
24 days ago | 5 days ago | |
Rust | Rust | |
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
cargo-raze
-
NixOS: Declarative Builds and Deployments
The same reason Bazel builds avoid using Cargo when building Rust software, so I'll describe why Bazel would do this:
- Bazel wants to cache remote resources, like each respective crate's source files.
- Bazel then wants to build each crate in a sandbox, and cache the build artifacts
This is an established practice, and Nix wants to drive the build for the same reasons.
See:
- https://github.com/bazelbuild/rules_rust
- https://github.com/google/cargo-raze
- Rust Is Portable
-
Regarding what happened to P0447: Why?
I can make much more sense of C++ code to ensure that two build systems produce the same effect than I can parse and learn two completely unconnected programming languages deeply enough to do the same. I can unit-test core routines. I can as easily extract core logic into shared (configuration) files etc. The benefit of a standard is not to discourage alternatives but rather to agree on definitive semantics and shared and common needs (that is: in this case needs for interfaces to the compiler/linker). The implementation and general availabilty is just one of the by-product. The ability to do introspection in common terms is maybe the most consequential other product, and this is critical for 'transpiling' to other build systems and writing automated adapters such as the one that bazel is recommend for cargo's dependency management.
-
What is your favorite programming language?
Cargo is not that tightly coupled with Rust. You can absolutely use bare rustc, and in fact people do that with other build systems like Bazel.
-
Six Years of Rust
Interesting, aren't the community-driven crates for these areas satisfactory enough? There's PROST and tonic, and quite well-used. I don't know about Bazel though, but I found this. Feel free to correct me on this subject, I admit I don't know that much about it.
-
Integrating Rust Into the Android Open Source Project | Google Security Blog
There is a project to generate Bazel BUILD files from Cargo.toml.
prost
-
Fivefold Slower Compared to Go? Optimizing Rust's Protobuf Decoding Performance
The benchmark is not comparing apples to apples.
prost is the most widely used Protobuf implementation in Rust, maintained by the Tokio organization. prost generates structs and serialization/deserialization code for you.
easyproto according to GitHib Search is used only by two projects. easyproto provides primitives for serializing and deserializing Protobuf, and requires hand writing code to do both.
A fair comparison would be prost vs google.golang.org/protobuf, or easyproto vs parts of quick-protobuf.
In most cases you can make Go as fast as Rust, but from my experience writing performance-sensitive code in Go requires significantly larger time investment and overall requires deeper language expertise. Pebble (RocksDB replacement in Go by CockroachDB) is a good example of this, the codebase is littered with hand-inlined[1] functions, hand-unrolled loops and it's not[2] even using Go memory management for performance critical parts, it's using the C memory allocator and manual memory management.
[prost]: https://github.com/tokio-rs/prost
- How Turborepo is porting from Go to Rust
-
Hey Rustaceans! Got a question? Ask here! (49/2022)!
You could use Protocol buffers to define a message type, then use prost to generate encoding/decoding code for that type.
- Adding #derive to a struct defined in another place
-
grpc gateway
Thanks but that doesn't seems to support `json_mapping` , there is a draft available but not sure when it will get merged https://github.com/tokio-rs/prost/pull/558
-
[help] Tonic-build: how to generate generic service definition?
Hi r/rust, I have a question regarding tonic-build (or prost-build).
-
Unwrapping inner values from the enum more easily?
Currently, I'm making some stuff by using protobuf via prost. Maybe you know, protobuf v3 treats all fields as optional, so it is pain to unwrap every nested field.
- Best way to communicate between Rust and Go?
-
Past, present and future of rust-protobuf
Note: one additional key feature currently missing from Prost is Proto2 extensions.
- Does prost [protocol buffers for rust] use tokio runtime to implement GRPC service?
What are some alternatives?
tonic - A native gRPC client & server implementation with async/await support.
rust-protobuf - Rust implementation of Google protocol buffers
prost - PROST! a Protocol Buffers implementation for the Rust Language
dmd - dmd D Programming Language compiler
varint-simd - Decoding and encoding gigabytes of LEB128 variable-length integers per second in Rust with SIMD
sccache - Sccache is a ccache-like tool. It is used as a compiler wrapper and avoids compilation when possible. Sccache has the capability to utilize caching in remote storage environments, including various cloud storage options, or alternatively, in local storage.
ts-proto - An idiomatic protobuf generator for TypeScript
Metals - Scala language server with rich IDE features 🚀
prost - PROST! a Protocol Buffers implementation for the Rust Language
pyroscope-rs - Pyroscope Profiler for Rust. Profile your Rust applications.
bytes - Utilities for working with bytes