Just published v1.0.0 of a single-purpose #rustlang crate, `conv`! Read about it here: https://myrrlyn.net/crates/conv
This crates lets you call `.into()` without making intermediate bindings or hitting compiler errors! I'd eventually like it to land in `core`, if it is well liked.
-
Show this thread
-
I plan to eventually publish a compendium crate that re-exports my utility crates, and make it *actually available on http://crates.io *, but not yet!
1 reply 0 retweets 2 likesShow this thread -
I wrote an RFC draft at http://myrrlyn.net/blog/rfcs/convert-trait … I would love a short review before I submit it to the
#rustlang RFCs repository1 reply 0 retweets 3 likesShow this thread -
saintly code wyzyrd Retweeted David Tolnay
per
@davidtolnay it now disables std correctlyhttps://twitter.com/davidtolnay/status/1069380910833840128 …saintly code wyzyrd added,
2 replies 0 retweets 2 likesShow this thread -
Replying to @myrrlyn
I would recommend again removing the "std" feature entirely and being unconditional no_std. Std crates can depend on no_std dependencies so a cfg is unnecessary.
1 reply 0 retweets 1 like -
Replying to @davidtolnay
For some reason I have the lingering memory of no_std not working on stable but I don't know why, but that was my reluctance to unconditionally no_std
1 reply 0 retweets 0 likes
No_std for libraries was stabilized in Rust 1.6! Importantly to reduce the `std = ["dep1/std", "dep2/std", "dep3/std", "dep4/std", ...]` situation.
-
-
Replying to @davidtolnay
"I really want to support 1.0 through 1.5" seems like a silly thing to say so I will go ahead and unconditionally no_std thanks again!
0 replies 0 retweets 0 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.