-
Notifications
You must be signed in to change notification settings - Fork 307
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Taking advantage of New Rust Features #558
Comments
It seems 2019 is indeed going to be the year of specialisation, const generics and GAT: rust-lang/rfcs#2657 🚀 🚀 |
Hey mates, this looks like something that new person like me can help. Do you see any thing that is easy to get start with? |
Any thoughts on @phungleson 's question? CC @jturner314 Also the |
Some suggestions:
|
looks like GATs are going to be part of stable next week |
Ideas and tracking to take advantage of “new” features in Rust
All features to be used because of what gain they give us, not to score points. Formulate goal & gain before implementing - and write it up the pull request 🙂.
target_feature
I'd prefer significant work in this area to take place in a separate crate, that we depend on. Something that gathers low level "loops" in one place. Like this, but revived and remade
const fn
(1.31)cargo fmt
on repository and add format checking to CI (now thatrustfmt
is stable).no_std
+alloc
. (1.36) no_std for ndarray #708MaybeUninit
(1.36) Change uninitialized to return an array of MaybeUninit #685and then on each item enabled by a specific feature, we add this:
(For an example, see async_compression.)
Future features (not relevant yet, because they don't exist in stable Rust)
Iterator::try_fold
(Try is unstable) Forward .try_fold(), .try_rfold() on the iterators when possible #706This is a tracking issue, please edit it.
The text was updated successfully, but these errors were encountered: