-
Notifications
You must be signed in to change notification settings - Fork 302
Announcing Rust 1.29 #268
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
Announcing Rust 1.29 #268
Conversation
Cc @rust-lang/release |
* `cargo fix` can automatically fix your code that has warnings | ||
* `cargo clippy` is a bunch of lints to catch common mistakes and improve your Rust code | ||
|
||
### `cargo fix` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it would be amazing if these could be contributed to the cargo docs and/or link to the cargo docs.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the cargo docs don't have this yet. I'll put it on my to-do list.
features: they're new abilities that Cargo has grown, and they're both about lints. | ||
|
||
* `cargo fix` can automatically fix your code that has warnings | ||
* `cargo clippy` is a bunch of lints to catch common mistakes and improve your Rust code |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is probably a product call that is not worth debating on this PR, but both of these deal with lints... we might want to specify that cargo fix won't fix cargo clippy lints (i am assuming that is tru)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems like this is specified on line 147-148.
The post is missing |
Proc macro API was also stabilized in 1.29. |
@petrochenkov Talking @Mark-Simulacrum users won't actually be able to use proc macros despite the API being stable. |
@Aaronepower |
In conversations with @alexcrichton it was my understanding that this cycle's stabilization with proc macros aren't quite as interesting as the next cycle's functionality for most end-users which is primarily why we're not really pushing it publicly; if that's not the case we can add it here I guess. |
Yes; that's why I didn't include it. I'd rather spend time explaining it all in the next release.
Yes! |
r? @rust-lang/core