case-studies
cross
case-studies | cross | |
---|---|---|
11 | 118 | |
1,603 | 5,965 | |
- | 2.2% | |
3.8 | 9.2 | |
about 1 month ago | 6 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.
case-studies
-
::lending-iterator — Lending/streaming Iterators on Stable Rust (and a pinch of HKT)
Luckily there is a workaround to emulate such a definition, which dtolnay discovered and explained here: https://github.com/dtolnay/case-studies/tree/b9802f6df8dc8e54970b83fb9af6df923b46abf5/unit-type-parameters.
-
Hey Rustaceans! Got a question? Ask here! (17/2022)!
I think they are talking about this one trick which the devs don't want you to know about. Note that while it looks like specialization, it works only in a few very limited cases and is quite fragile, so it's a hack, not a substitute for the real feature.
-
Any good resources for learning Rust macros?
Also I suggest his case studies repo since you are looking at what is possible: https://github.com/dtolnay/case-studies
-
What are some creative/advanced uses of macro_rules?
/u/dtolnay has a great case studies repository.
-
Hey Rustaceans! Got an easy question? Ask here (29/2021)!
Once you have the basics down, read dtolnay's case studies. They show how to do advanced stuff with easy macros.
-
println use `Debug` if argument is not `Display`
If you were writing your own println macro, you might be able to get away with this kind of hack: https://github.com/dtolnay/case-studies/blob/master/autoref-specialization/README.md
-
Hey Rustaceans! Got an easy question? Ask here (11/2021)!
You can use "Autoref-based stable specialization" or use/mimic the impls crate.
-
Why I gave up on Rust (for now)
With a subset of specialization likely riding the trains soon and a workaround available, why would you give up?
-
Hey Rustaceans! Got an easy question? Ask here (10/2021)!
this works since values and types are in different namespaces (see: Rusts Universes or dtolnay's Case Study about "Unit struct with type parameters")
-
Hey Rustaceans! Got an easy question? Ask here (53/2020)!
To do this with traits you would need specialization but since you are using macros you should be able to use "Autoref-based stable specialization". Here is a playground which uses the latter approach to implement the wanted macro without using any nightly features.
cross
-
Is statically compiling against glibc possible?
To compile a program with musl on a glibc system you can use cross-rs!
-
How to cross Compile on Debian for: Mac / FreeBSD / OpenBSD / Android ... ?
I cross compile to Mac, bsd, windows, etc cross ... Works great for me with either docker or podman.
-
Compiling against specific version glibc
If docker is available for you, https://github.com/cross-rs/cross is another and reliable way to solve this kind of problem. I do use it regularly.
-
Transitioning to Rust as a company
We are using https://github.com/cross-rs/cross.
-
A guide to cross-compilation in Rust
There is some built-in support in rustc for cross-compiling, but getting the build to actually work can be tricky due to the need for an appropriate linker. Instead, we’re going to use the Cross crate, which used to be maintained by the Rust Embedded Working Group Tools group.
-
Is there a definitive guide on cross-compiling with OpenSSL?
I have used cross before to cross compile from Linux to other Linux. It has a section on it's wiki about this. Maybe that could be of help.
-
Docker ARMv7 Alpine Rust builder
You can use cross to build your application and copy the artifacts into an alpine armv7 container. It would also build faster due to using cross compilation rather than QEMU.
-
Compiling Linux to Mac in CI/CD
Looks like cross is the easiest way to get something cross-compiled but its Mac support is blocked behind building your own build image. Even that repo says that it might be broken.
-
How to you develop in containers?
Bonus: if you’re working with Rust and doing a lot of cross platform stuff, check out cross. It runs QEMU in docker so you can run tests on a bunch of different emulated targets easily- literally a one line setup, it’s kind of magical.
-
What are some stuff that Rust isn't good at?
It's also not as naturally cross-compilable as Go, though that's partly a side-effect of not accepting being a semi-closed ecosystem to achieve that and cross exists as a stop-gap while things like cargo-zigbuild explore less drastic options.
What are some alternatives?
rocket-auth-login - Authentication and login processing for Rust's Rocket web framework. Demonstrates a working example of how to authenticate users and process login as well as how to handle logging out.
dockcross - Cross compiling toolchains in Docker images
xargo - The sysroot manager that lets you build and customize `std`
termux-adb-fastboot - android adb-fastboot tools for termux
proc-macro-crate - `$crate` in procedural macros.
opencv-rust - Rust bindings for OpenCV 3 & 4
mini-redis - Incomplete Redis client and server implementation using Tokio - for learning purposes only
rusqlite - Ergonomic bindings to SQLite for Rust
parquet2 - Fastest and safest Rust implementation of parquet. `unsafe` free. Integration-tested against pyarrow
plotters - A rust drawing library for high quality data plotting for both WASM and native, statically and realtimely 🦀 📈🚀
cargo-expand - Subcommand to show result of macro expansion
homebrew-macos-cross-toolchains - macOS cross compiler toolchains