portable-simd
cargo-xtask
portable-simd | cargo-xtask | |
---|---|---|
19 | 26 | |
816 | 736 | |
2.0% | - | |
8.7 | 3.0 | |
21 days ago | 10 months ago | |
Rust | ||
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.
portable-simd
- Rust-lang/portable-SIMD: The testing ground for the future of portable SIMD
-
Let's thank who have helped us in the Rust Community together!
Jubilee and Caleb Zulawski for their tireless work on the portable SIMD project. It will land, some day, and when it does it's going to be an amazing boon for the project.
-
Mutually aligned vectors?
The portable SIMD project implements an as_simd() function for slices. The basics are that you get 3 slices and the middle one is a SIMD slice. It allows for fast aligned loads of the data, which could matter if your algorithm is becoming memory bound; it is also a convenient and safe abstraction. In my case, I actually have 2 vectors (say, x and y). I can take them apart using as_simd() like so:
- Code review: deinterlacing a RGBA colour buffer with std::simd
-
Base64 Encoding Performance: Java vs Rust
Rust has generics and monomorphization. You can write the algorithm once and compile for multiple targets. rust-lang/portable-simd
-
Zen4's AVX512 Teardown
This Rust issue [0] was the best short summary of what an SIMD Shuffle is I could find:
„A "shuffle", in SIMD terms, takes a SIMD vector (or possibly two vectors) and a pattern of source lane indexes (usually as an immediate), and then produces a new SIMD vector where the output is the source lane values in the pattern given.“
[0] https://github.com/rust-lang/portable-simd/issues/11
-
possibility of blas natively in Rust
Yet by default it generates code which is only compatible with Pentium4 or newer. In fact lots of serious issues relate to older CPUs and rustc developers plan is to declare them closed when they would be able to drop i686 support (all AMD CPUs which support SSE2 support x86-64, too while Intel situation is mess).
-
Best portable simd library for stable rust?
The standard API crate for portable simd is at https://github.com/rust-lang/portable-simd, but using this requires nightly, which I don't want to do. I'd like to use a crate for simd that works on both x86_64 and wasm in stable rust. wide looks fine for this purpose. Are there any potentially better choices?
-
Any plans for built-in support of Vec2/Vec3/Vec4 in Rust?
See: https://github.com/rust-lang/portable-simd
-
Hey Rustaceans! Got a question? Ask here! (28/2022)!
As for portable SIMD, there's relatively recent activity (last commit 20 days ago) on this repository: https://github.com/rust-lang/portable-simd
cargo-xtask
-
🏃♂️ Use task.go for your Go project scripts
💡 Inspired by matklad/cargo-xtask and based on 🏃♂️ Write your Rust project scripts in task.rs from the Rust ecosystem.
-
clap_completion help requested
Using a cargo-xtask task to generate them as a manual step (inlyne currently does this)
- Cargo xtask: extend cargo with custom commands written in Rust
-
Including a cargo command as a dev dependency
As someone else said just is good for that job, or you could implement an xtask helper for these things and setup a suitable development environment with that: https://github.com/matklad/cargo-xtask/
- Cargo xtask: extend stock, stable cargo with custom commands written in Rust
-
Going beyond build.rs: introducing cargo-px
Well tools like cornucopia, prisma-rust-client, protoc-gen-tonic, they don't generate in build.rs, but instead provide either a cli to be called ahead of time, or provide a library that can be called by your own binary (which should generally follow the xtask pattern)
- Hey Rustaceans! Got a question? Ask here (17/2023)!
-
Best way to include a utility command for my crate?
If I understand, this is a tool for when working on the project itself? Akin to a helper script? You could go the cargo install route as already pointed out but there is also the xtask convention.
-
We have getrandom at home
For simple cli apps for internal use, such as cargo-xtasks, I prefer pico_args due to its fast compile times.
-
Rust for Web Development | An Honest Evaluation
For developer-oriented stuff, there's tools like xshell and cargo-xtask. For operator tasks that need to run in a deployed environment, it's not usually a big lift to add CLI subcommands to your binary. It's certainly more boilerplate and inertia than doing stuff in a live REPL, though, and sometimes difficult to recommend for truly one-off situations.
What are some alternatives?
fast_image_resize - Rust library for fast image resizing with using of SIMD instructions.
just - 🤖 Just a command runner
rust-base64 - base64, in rust
cargo-make - Rust task runner and build tool.
faster-hex - fast hex
bors-ng - 👁 A merge bot for GitHub Pull Requests
config-rs - ⚙️ Layered configuration system for Rust applications (with strong support for 12-factor applications).
rust - Empowering everyone to build reliable and efficient software.
cargo-about - 📜 Cargo plugin to generate list of all licenses for a crate 🦀
waihona - Rust crate for performing cloud storage CRUD actions across major cloud providers e.g aws
ulid-rs - This is a Rust implementation of the ulid project
fzf - :cherry_blossom: A command-line fuzzy finder