Our great sponsors
buck2 | evcxr | |
---|---|---|
31 | 75 | |
3,259 | 5,131 | |
3.0% | 2.2% | |
10.0 | 8.7 | |
about 10 hours ago | 24 days ago | |
Rust | Rust | |
Apache License 2.0 | GNU General Public License v3.0 or later |
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.
buck2
-
Tech Debt: My Rust Library Is Now a CDO
https://buck2.build/ https://github.com/facebook/buck2
Rust support is also rather good ;) https://github.com/facebookincubator/reindeer
-
Things I learned while building projects with NX
Buck 2 by Facebook
-
Declarative Gradle is a cool thing I am afraid of: Maven strikes back
NOTE: I won’t mention SBT and Leiningen here because, with all due respect, they are niche build tools. I also won’t discuss Kobalt for the same reason (besides, it’s no longer actively maintained). Additionally, I won’t touch upon Bazel and Buck in this context, mainly because I’m not very familiar with them. If you have insights or comments about these tools, please feel free to share them in the comments 👇
-
Reason to use other Build Tool than Make?
There're tools which do this, for example https://bazel.build/, and https://buck2.build/ However they have a learning curve, which might be steep for some folks.
There's a new build system which works on similar ideas to buck: https://buck2.build/
-
Hello r/Rust! We are Meta Engineers who created the Open Source Buck2 Build System! Ask us anything! [Mod approved]
Great question! Our approach has been to use Bxl (https://buck2.build/docs/developers/bxl/) to script up operations that call various subtargets like `[compilation-database]` for `cxx_library`. I don't think all these pieces are open source yet, but https://github.com/facebook/buck2/blob/main/prelude/rust/rust-analyzer/resolve_deps.bxl is a snippet that is used to drive Rust Analyzer. Bxl does seem to be the "missing piece" for mapping between what the build system wants and what the IDE wants. But there's still a bunch of work after you get there to plumb into LSP.
I don't think all these pieces are open source yet, but https://github.com/facebook/buck2/blob/main/prelude/rust/rust-analyzer/resolve_deps.bxl is a snippet that is used to drive Rust Analyzer
See https://github.com/facebook/buck2/tree/main/shim/third-party/rust/fixups for the list of fixups. I'd say it is slightly trending down, as more people stabilise around libraries such as rustix for OS-specific functionality. But I'd say that a better approach would be for Reindeer to ship a default set of fixups for most common libraries, so it was shared. We haven't tracked fixups over time.
The recent blog about Buck2 and our GitHub.
The way it's done internally (and which we think is a good way to do it) is to implement the linter in two stages. In your Buck rules, you have something that produces outputs that describe transformations that need to be done, then an external binary calls Buck2 to produce those outputs. That binary can then apply the transformations that were requested. There are some examples and a bit more discussion over here: https://github.com/facebook/buck2/issues/115 -Thomas O. What are the long term plan to manage prelude / third party rules? I.e. if there is a repository for rules typescript / ruby, how should a user go about downloading them and keeping the version up-to-date?
evcxr
-
Scriptisto: "Shebang interpreter" that enables writing scripts in compiled langs
Emacs didn't invent REPL, and it's common everywhere. For Rust: https://github.com/evcxr/evcxr/blob/main/evcxr_repl/README.m.... But heck, the compiler is reasonably fast enough that any IDE can REPL by compiling the code.
The value here is more in being able to read a script before you run it, then have it run fast, maybe tweaking something here and there. And a compiled script will run 10,000 times faster than LISP, which can be important.
-
Go: What We Got Right, What We Got Wrong
https://github.com/evcxr/evcxr can run Rust in a Jupyter notebook. It's not Golang but close enough.
-
The Hallucinated Rows Incident
The engine uses rust_decimal::Decimal to represent high precision decimal numbers, like the weight property. Serialization of RocksDB keys is done by the storekey crate. To know how Yumi's machine stores diffs, we can now ask- How does storekey serialize rust_decimal? Well, using evcxr to run Rust in Jupyter, the answer is as a null-terminated string:
- TermiC: Terminal C, Interactive C/C++ REPL shell created with BASH
- Exploring Options for Dynamic Code Changes in Rust without Recompilation (hot reloading)
- Go 1.21 will (likely) have a static toolchain on Linux
-
What’s an actual use case for Rust
In theory you should be able to create Rust notebooks (Jupyter notebook) using evcxr so maybe some AI, data analysis, prototyping make sense if you aim for good performance in final application (protype in evcxr and use notebook as reference to implement final application in Rust for speed and safety).
-
would you use rust for scripting?
You should check out evcxr
- Nannou – An open-source creative-coding framework for Rust
-
A Case for Rust in Deep Learning
I think you might like this project: https://github.com/google/evcxr . It brings the REPL workflow to Rust, so having fast iteration should not be an issue.
What are some alternatives?
vscode-jupyter - VS Code Jupyter extension
polars - Dataframes powered by a multithreaded, vectorized query engine, written in Rust
jupyter-rust - a docker container for jupyter notebooks for rust
turbo - Incremental bundler and build system optimized for JavaScript and TypeScript, written in Rust – including Turbopack and Turborepo.
rust-script - Run Rust files and expressions as scripts without any setup or compilation step.
bincode - A binary encoder / decoder implementation in Rust.
cargo-script - Cargo script subcommand
iron.nvim - Interactive Repl Over Neovim
vim-slime - A vim plugin to give you some slime. (Emacs)
ipython - Official repository for IPython itself. Other repos in the IPython organization contain things like the website, documentation builds, etc.
nsi - High level Rust bindings for Illumination Research’s Nodal Scene Interface – ɴsɪ.
rust-csv - A CSV parser for Rust, with Serde support.