derive_more
smallnum
derive_more | smallnum | |
---|---|---|
3 | 1 | |
1,406 | 7 | |
- | - | |
7.7 | 1.8 | |
13 days ago | over 2 years ago | |
Rust | Rust | |
MIT License | MIT License |
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.
derive_more
-
derive_more: can it be used to handle operator overloads for borrowed references?
Is there a way to use derive_more to handle the generation of binary operators with one or both referenced operands? For example, avoiding having to do this macro dance for every combination of MyVal and &MyVal, for every operator needed:
-
Is there a convenient way to convert a struct<T> (where all fields are of type T) into struct<U> where U: From<T>?
This fails to compile. Looking at the implementation for that macro I don't see a way to use it that would work: https://github.com/JelteF/derive_more/blob/master/impl/src/from.rs
-
Microsoft re-adds .NET hot-reload
tl;dr you can put commit hashes in the place where the parent comment put tags.
The PR interface actually exposes this for force-pushes, but the UI discovery for this is horrible. It turns out that the "force-pushed" part in the little message in the github UI is actually a link. This link points to the diff between the old and the new HEAD of the branch.
As an example you can look at this PR:
It has this little message somewhere down the page:
Monadic-Cat force-pushed the add-unwrap branch from e130dbe to 25235aa 4 months ago
If you then click that link you go to the "compare" page, which shows the diff between the two commits:
https://github.com/JelteF/derive_more/compare/e130dbe6b2a429...
Disclaimer: I'm a Micrsoft employe, but don't work on Github. I'm a daily user of Github though.
smallnum
-
"smallnum" crate: compile-time size optimization for numeric primitives
Thus, this crate provides a macro to automatically determine the smallest integer type that can "fit" a constant max. When the size of a backing collection is known at compile-time (e.g. when using crates like `smallvec` for `!#[no_std]` development), this compile-time optimization can help save precious bytes - potentially for every node in an index-based structure (see README examples). Currently supports signed and unsigned numbers, but I’d love help with floating point support if anyone has ideas (though I don't know what a realistic usecase would be :P).
What are some alternatives?
rust-derive-builder - derive builder implementation for rust structs
deranged - Proof of concept ranged integers in Rust.
rust-cpp - Embed C++ directly inside your rust code!
rust-bitfield - This crate provides macros to generate bitfield-like struct.
num - A collection of numeric types and traits for Rust.
syn-rsx - syn-powered parser for JSX-like TokenStreams
rfcs - RFCs for changes to Rust
pipe-trait - Make it possible to chain regular functions
Visual Studio Code - Visual Studio Code