Rustup
cargo-release
Our great sponsors
Rustup | cargo-release | |
---|---|---|
58 | 10 | |
5,807 | 1,224 | |
1.8% | 2.5% | |
9.4 | 8.8 | |
6 days ago | 11 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.
Rustup
-
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).
-
Announcing Rustup 1.26.0 | Rust Blog
Hmm. No motivation description in the commit. https://github.com/rust-lang/rustup/pull/3044/commits/f887c19082eca77f33db282ca87eb3706c444098
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
-
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
-
installer bug; darwin aarch64 pkg wants Rosetta
Done https://github.com/rust-lang/rustup/issues/3197
cargo-release
-
Oxlint – written in Rust – 50-100 Times Faster than ESLint
You should combine step 1 and 2 with CI. Just tag a version in your git, push to remote and have CI auto build a release for you.
Use github actions or other setup for other backends.
Or go nuts with cargo-release.
-
Rust 2030 Christmas list: Subcrate dependencies
tools like cargo-release
-
`toml` vs `toml_edit` (ie `toml` 0.6 is out)
Just to check, are you aware of cargo-edit's cargo-set-version or cargo-release?
-
What's everyone working on this week (45/2022)?
I released my first crate that provides a derive macro to easily obtain a name of a current variant in an enum as a string. I did it mostly to learn about procedural macros and the process of releasing a crate. I then found out there is strum which does this and much more. Nonetheless, I learned a lot and I found couple of nice tools like ```cargo-release and git-cliff.
-
A GitHub Action for creating "Release PRs" for Cargo projects.
I'll note there is an issue in the cargo-release repo where this kind of workflow is wanted. https://github.com/crate-ci/cargo-release/issues/119
-
[Gitoxide December Update]: a new object database and upcoming multi-pack index support
cargo-release is on about the same level of features used
-
Introducing `cargo smart-release` - the new way to release workspace crates
Yes, developers from all three tools were sharing ideas with each other recently
-
🦀 Publishing My First Rust Crate
Use cargo-release and setup pre-release hooks and replacements.
What are some alternatives?
rust - Empowering everyone to build reliable and efficient software.
rust-mode - Emacs configuration for Rust
rust-on-raspberry-pi
Rust for Visual Studio Code
Rust Language Server - Repository for the Rust Language Server (aka RLS)
cargo-modules - Visualize/analyze a Rust crate's internal structure
cargo-update - A cargo subcommand for checking and applying updates to installed executables
just - 🤖 Just a command runner
cargo-make - Rust task runner and build tool.
Clippy - A bunch of lints to catch common mistakes and improve your Rust code. Book: https://doc.rust-lang.org/clippy/
gdbgui - Browser-based frontend to gdb (gnu debugger). Add breakpoints, view the stack, visualize data structures, and more in C, C++, Go, Rust, and Fortran. Run gdbgui from the terminal and a new tab will open in your browser.
CodeLLDB - A native debugger extension for VSCode based on LLDB