reference VS cargo-make

Is perfectly valid Rust code. And there's reborrow, too.

I truly appreciate how much effort u/ehuss puts into maintaining The Rust Reference, considering that documenting stuff is not usually a fun task people want to do. Not to mention that ehuss is also the Cargo team lead, responsible for developing one of the most loved tools in Rust. ehuss's insightful knowledge always ensures that Cargo works without unexpected surprises.

Here is (somewhat long) discussion on the topic with other examples: https://github.com/rust-lang/reference/issues/788

The PR for updating the documentation is here, still under discussion: https://github.com/rust-lang/reference/pull/1055

thank you this is definitely interesting and i need to read more. For anyone else, this is the thing I found about this issue when I looked it up. It's a github issue about how little documentation there is on the subject and that there should be more. Even the initial post has a lot of interesting details and links. Thanks for bringing it up although sorry it seems your comment went a bit over the heads of some redditors.

⭐ The Rust Reference - repo

For the rust reference, there is an open pull request https://github.com/rust-lang/reference/pull/1265/

&mut * is reborrowing which is allowed

Officialhttps://www.youtube.com/watch?v=rAl-9HwD858&list=PLqbS7AVVErFiWDOAVrPt7aYmnuuOLYvOa The official rust book Rust by example The rust docs Rustlings the most fun way imo

I've opened a PR to add this more prominently to the Conditional Compilation entry in the Rust reference.

cargo-make aims to be an extensive Rust-written task runner that additionally lets you define workflows to execute your tasks. You can install it using cargo install cargo-make.

You might be interested in cargo-make, which is based on TOML, or Just, which has a syntax that is vaguely inspired by Make but much less weird sigils and more suited to non-file-based tasks.

I would like to rewrite this project in Rust, but I am not so familiar with Cargo as I am with Make. Is it possible to declare these kinds of rules and targets ? Should I use a build script, a custom tool like cargo-make or something else ? What do you think ?

I use just myself, and I personally don't want projects' codebase to decide when something gets cargo installed on my system. For people who feel that's more acceptable, I'll note that cargo-make has first class support for the idea of expressing a task that depends on a cargo plugin:

Thank you for the help, created ticket #787 and #788!

https://github.com/sagiegurari/cargo-make

I ended up using it over just because it felt easier to use cross platform, and toml seemed like a right choice

cargo make is used pretty extensively in Bottlerocket OS

Cargo is a pretty robust build tool on it's own, but for that extra automated workflow oomph, I also use cargo-make