-
Could you please publish Rust crates to crates.io, the last update there was 4 months ago.
-
Right now, every Rust package is an ecosystem unto itself, with dependency versions being selected from each package’s upstream `Cargo.lock` file (or a vendored one if none is present). This stands in…
-
I build `bazel-lsp 0.6.1` from source and I'm using it as a LSP in `helix`. GoToDefinition on labels works, but completion doesn't seem very accurate or context aware. Here's a few examples:
1. I'd…
-
We recently published our `protocols` crates to `crates.io`.
We need to make sure the APIs provided by those crates are properly documented under the [Rust Best Practices](https://doc.rust-lang.org/r…
-
Currently, all of Rust's releases and all crates are stored on AWS. While we have multiple measures in place to prevent accidental deletion of releases or crates, e.g. bucket replication to a differen…
-
Bazel has changed its repository name separator character from `~` to `+` so `rules_rust~~rust_host_tools~rust_host_tools` become `rules_rust++rust_host_tools+rust_host_tools`. These `+`s conflict wi…
-
Bazel: 7.3.0
rules_rust: 0.49.1
rust: 1.80.1
This issue hit me totally out of the blue today;
rust_prost_toolchain somehow generates different aliases on on Linux / X86 than used in
the pros…
-
Continuation of the discussion in #372
We should start publish our rust crates to crates.io. For that I can see some questions:
- naming: as pointed out by @alecandido on crates.io we can be call…
-
I might have missed it in the docs, but could this crate (perhaps /nightly) solve the "encapsulated components" problem that a lot of CSS in Rust crates are challenged with? Currently it's quite the h…
-
shaodwsocks-rust has separated the protocol into a separate crate https://crates.io/crates/shadowsocks
Should we use this instead of implementing it ourselves?