Rustup
rust-on-raspberry-pi
Our great sponsors
| Rustup | rust-on-raspberry-pi | |
|---|---|---|
| 58 | 1 | |
| 5,866 | 290 | |
| 1.6% | - | |
| 9.5 | 0.0 | |
| 4 days ago | - | |
| Rust | Shell | |
| 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.
Rustup
-
Problem with rust-analyzer in helix
I got it to finally work by following this
-
Do you use relative toolchain paths with rustup? Let us know!
If you are someone actively using such relative-path toolchains, please contact us (Discord / Github issues).
-
Canonical hiring Rust toolchain dev
We had a snap package; we removed it in mid 2022
-
Announcing Rustup 1.26.0 | Rust Blog
I don't know. The PR references prior discussion without a link, so it may have been private.
- Foundation - Open Membership
-
Telemetry really goes into Go toolchain, no matter what
As long as he doesn't put hidden folders in your root like rust. https://github.com/rust-lang/rustup/issues/341
-
telemetry in the go toolchain? just say no...
I think you're being upvoted by folks who don't know better, which is a shame because you're making things up :/. The telemetry feature in rustup kept everything local and never "pinged home". And you had to enable it with a command `rustup telemetry enable`. And it just logged JSON files at the path you mentioned. By 2019, the feature was disabled (see: https://github.com/rust-lang/rustup/issues/341 ) because no one worked on it and it just gathered bugs.
-
Go claims telemetry objectors arguing in bad faith and violating Code of Conduct
FWIW, there is a proposal to add telemetry to LLVM [0] and Rust used to have telemetry [1], both off by default. Some things in the node.js world have telemetry enabled by default, like Next.js [3].
Some people are posting here as if this as already decided -- AFIACT, that's not the case. It's not even a formal proposal yet, and the stated intent was to start a conversation around something concrete. (For context, this is standard for how I've seen the Go project approaches large topics, including for example I think there were something like ~8 very detailed generics design drafts from the core Go team over ~10 years).
It sounds like the Go team is going to take some time to look into some of the alternative approaches suggested in the feedback collected so far.
In any event, this is obviously a topic people are very passionate about, especially opt-in vs. opt-out, but I guess I would suggest not giving up hope quite yet.
[0] https://discourse.llvm.org/t/rfc-lldb-telemetry-metrics/6458...
-
Google's Go may add telemetry reporting that's on by default
Rust (Specifically Rust Up) seems to have planned to include telemetry but they paused and cancelled the decision, possibly after implementing it initially.
-
Who "owns" Rust ?
https://github.com/rust-lang/rustup/issues/341 and rust installation uses telemetry
rust-on-raspberry-pi
-
Anything C can do Rust can do Better
Cross Compiling for Raspberry Pi - Ogeon
What are some alternatives?
rust - Empowering everyone to build reliable and efficient software.
rustfmt - Format Rust code
rust-mode - Emacs configuration for Rust
rust-musl-cross - Docker images for compiling static Rust binaries using musl-cross
Rust for Visual Studio Code
crate-deps
Rust Language Server - Repository for the Rust Language Server (aka RLS)
MIRAI - Rust mid-level IR Abstract Interpreter
cargo-modules - Visualize/analyze a Rust crate's internal structure
Clippy - A bunch of lints to catch common mistakes and improve your Rust code. Book: https://doc.rust-lang.org/clippy/
cargo-release - Cargo subcommand `release`: everything about releasing a rust crate.
Racer - Rust Code Completion utility