nutype | xshell | |
---|---|---|
7 | 10 | |
1,209 | 637 | |
- | - | |
8.9 | 5.0 | |
27 days ago | 20 days ago | |
Rust | Rust | |
MIT License | 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.
nutype
- Nutype 0.4.0 released
- Nutype 0.3.0 released
-
Nutype 0.2.0 is released.
The release notes: https://github.com/greyblake/nutype/releases/tag/v0.2.0
-
Rust for Web Development | An Honest Evaluation
Regarding your macro system for "new nominal types" - are you talking about something in the vein of nutype or prae?
-
Nutype: the newtype with guarantees
I need some time to think about this. If you don't mind I pasted your message to a Github discussion , so I don't forget it: https://github.com/greyblake/nutype/discussions/11
xshell
- Hey Rustaceans! Got a question? Ask here (17/2023)!
-
would you use rust for scripting?
Just a few minutes ago I learned about https://github.com/matklad/xshell and it looks nice!
-
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.
- Started using Rust for scripting
-
Rust as bash scripting replacement?
how was your experience with trying to use [xshell](https://github.com/matklad/xshell/) as a shell script replacement? was the boilerplate worth it?
-
How to improve my Rust workflow?
Also xshell might be helpful here https://github.com/matklad/xshell
-
Rust Support in the Linux Kernel
* time to compile whatever syn generated
I didn’t do a super thorough studies of things, but my impression is that 2, performance of syn itself, is rarely an issue. Most of the time it is 1) (and the associated problem of decreased build parallelism because half of the crates wait for syn to compile) and 3).
To get a feeling how costly a simple proc macro is, run this benchmark: https://github.com/matklad/xshell/blob/4e5090e9f79baeed1037b....
-
cradle: Run child processes with ease
This is an API vulnerable to shell injection. I think it’s relatively important to design command-running libraries which don’t re-introduce the possibility of this error into Rust. The fix here is to ensure that the string is a compile-time string, and, preferably, even lex it at compile time. See xshell for an example of ergonomic and safe API here: https://github.com/matklad/xshell.
-
The Plan for the Rust 2021 Edition
Note that “lexer level” proc macros, which don’t parse rust code, and which don’t generate a ton of Rust code, could be pretty light weight on compile times. Here’s a benchmark one can run to measure that: https://github.com/matklad/xshell/blob/master/tests/it/main.rs#L376
What are some alternatives?
hado-rs
rfcs - RFCs for changes to Rust
pad-motion - Implementation of Cemuhook gamepad motion protocol.
Cradle - Play Twine stories in Unity.
r4d - A macro processor made with rust, which aims to be a modern alternative to m4 macro processor.
compiler-explorer - Run compilers interactively from your web browser and interact with the assembly
windows-drivers-rs - Platform that enables Windows driver development in Rust. Developed by Surface.
rust - Empowering everyone to build reliable and efficient software.
enum-code - derive(Code) simplifies error handling by providing an easy-to-use enumeration of error codes
hashira-templates - Starter templates for hashira
identicon-rs - A simple identicon implementation in rust
evcxr