Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upUpdated releases notes for 1.19 #42503
Conversation
rust-highfive
assigned
aturon
Jun 7, 2017
This comment has been minimized.
This comment has been minimized.
|
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @aturon (or someone else) soon. If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes. Please see the contribution instructions for more information. |
This comment has been minimized.
This comment has been minimized.
|
In this release there has been a lot of error codes added by @GuillaumeGomez I was wondering should they each get a line item, or is the current fine? |
jtdowney
reviewed
Jun 7, 2017
| -------- | ||
|
|
||
| - [Numeric fields can now be used for creating tuple structs.][36868] | ||
| For example `struct Point(u32, u32); let x = Foo { 0: 7, 1: 0 };`. |
This comment has been minimized.
This comment has been minimized.
Nemo157
reviewed
Jun 7, 2017
| the members in a given workspace.][cargo/3988] | ||
| - [Updated `libssh2-sys` to 0.2.6][cargo/4008] | ||
| - [Target directory path is now in the cargo metadata][cargo/4022] | ||
| - [Cargo no longer checks the crates.io index locally][cargo/4026] This should |
This comment has been minimized.
This comment has been minimized.
Nemo157
Jun 7, 2017
Contributor
I would word this something like "Cargo no longer checks out a local working directory for the crates.io index"
ollie27
suggested changes
Jun 7, 2017
| - [Ending a float literal with `._` is now a hard error. | ||
| Example: `42._` .][41946] | ||
| - [Ending a str literal with an underscore is now a hard error | ||
| Example: `"foo"_`][41990] |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
| - [Added `rust-windbg.cmd`][39983] for loading rust `.natvis` files in the | ||
| Windows Debugger. | ||
| - [Rust Language Server is now packaged as a non default component with the | ||
| `.exe`, `.msi`, and `.pkg` installers][42306] |
This comment has been minimized.
This comment has been minimized.
petrochenkov
reviewed
Jun 7, 2017
| Language | ||
| -------- | ||
|
|
||
| - [Numeric fields can now be used for creating tuple structs.][36868] |
This comment has been minimized.
This comment has been minimized.
petrochenkov
reviewed
Jun 7, 2017
| - [Ending a str literal with an underscore is now a hard error | ||
| Example: `"foo"_`][41990] | ||
| - [Publicly exposing a private type is now a hard error][34537] This was | ||
| previously a warning. |
This comment has been minimized.
This comment has been minimized.
petrochenkov
Jun 7, 2017
Contributor
Nah, this is wrong. Most of #34537 isn't going to be an error, only some tiny piece of it (public reexports of private enum variants) has become an error.
petrochenkov
reviewed
Jun 7, 2017
| - [Publicly exposing a private type is now a hard error][34537] This was | ||
| previously a warning. | ||
| - [Type parameter defaults in trait impls and functions is now a | ||
| hard error][36887] This was previously a warning. |
This comment has been minimized.
This comment has been minimized.
petrochenkov
Jun 7, 2017
Contributor
This is still a warning, there was too much breakage (as you can see, the issue is still open).
petrochenkov
reviewed
Jun 7, 2017
| - [Type parameter defaults in trait impls and functions is now a | ||
| hard error][36887] This was previously a warning. | ||
| - [`use` imports on a private `extern crate` in a module is now a hard | ||
| error.][36886] This was previously a warning. |
This comment has been minimized.
This comment has been minimized.
petrochenkov
Jun 7, 2017
Contributor
#36886 is about any use of private extern crates outside of their module, not about imports or reexports.
mbrubeck
reviewed
Jun 7, 2017
|
These look great! Here are a few additions that I think would clarify some of them. |
| For example: `let x = loop { break 7; };` | ||
| - [C compatible `union`s are now available.][42068] They can only contain `Copy` | ||
| types and cannot have a `Drop` implementation. | ||
| Example: `union Foo { bar: u8 }` |
This comment has been minimized.
This comment has been minimized.
mbrubeck
Jun 7, 2017
Contributor
A union with two fields of different types might be a clearer example.
mbrubeck
reviewed
Jun 7, 2017
| Compiler | ||
| -------- | ||
|
|
||
| - [Added bootstrap support for Android.][41370] |
This comment has been minimized.
This comment has been minimized.
mbrubeck
Jun 7, 2017
Contributor
I suggest expanding this to "Add support for bootstrapping the Rust compiler toolchain on Android."
|
|
||
| - [Added bootstrap support for Android.][41370] | ||
| - [Change `arm-linux-androideabi` to correspond to the `armeabi` | ||
| official ABI.][41656] |
This comment has been minimized.
This comment has been minimized.
mbrubeck
Jun 7, 2017
•
Contributor
It might be useful to note that developers must now use --target armv7-linux-androideabi if they want to continue targeting the armeabi-v7a ABI.
This comment has been minimized.
This comment has been minimized.
|
Should this now mention LLVM4 support? (i.e. rust-llvm is upgraded, and external LLVM4 works too.) |
TimNN
reviewed
Jun 7, 2017
| Example: `union Foo { bar: u8 }` | ||
|
|
||
| Compiler | ||
| -------- |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
aidanhs
added
the
S-waiting-on-review
label
Jun 7, 2017
This comment has been minimized.
This comment has been minimized.
|
@brson on the rust side, XZ compression of the tarballs should ready. Should it be mentioned in the release notes or is it better to wait for the next rustup release? |
This comment has been minimized.
This comment has been minimized.
|
@Aaronepower There are two sides to it, both the version of LLVM that Rust is shipped with and the external versions it supports in custom builds. For the LLVM 3.9 update it simply said, "The compiler can now be built against LLVM 3.9". |
This comment has been minimized.
This comment has been minimized.
|
Thanks a bunch @Aaronepower. Added a link to the rendered notes to the OP. @Aaronepower do any of these have RFC's that can be referenced for further info? I bet numeric fields, break return, unions, maybe closure coercions. I see that 'compatibility notes' is not last this time. Any particular reason? I've put them last in the past to deemphasize them. I don't see custom CRT linkage, xz compression. I've added a milestone issue to make sure rustup with xz gets released: #42542 |
This comment has been minimized.
This comment has been minimized.
|
@ranma42 Yes, I think it should be mentioned. rustup will be out in time. |
This comment has been minimized.
This comment has been minimized.
|
@Aaronepower I think one line for the error codes is fine. |
carols10cents
added
S-waiting-on-author
and removed
S-waiting-on-review
labels
Jun 12, 2017
This comment has been minimized.
This comment has been minimized.
|
ping @Aaronepower, just wanted to keep this on your radar! |
This comment has been minimized.
This comment has been minimized.
|
I think rust-lang/cargo#3954 (Add support for custom target-specific runners — |
This comment has been minimized.
This comment has been minimized.
|
It is possible the RangeArgument type will change names before release: #43033 |
This comment has been minimized.
This comment has been minimized.
|
RangeArgument is not in the release. |
This comment has been minimized.
This comment has been minimized.
|
Updated for all comments. #42635 is slated to be fixed and doesn't need a compat note. We might wait to see that reverted and then this is probably good to go. |
mbrubeck
reviewed
Jul 13, 2017
| a warning. | ||
| - [From the pound escape, lines consisting of multiple `#`s are | ||
| now visible][41785] | ||
| - [`for` loop desugaring has changed such that `break` does nat |
This comment has been minimized.
This comment has been minimized.
mbrubeck
reviewed
Jul 13, 2017
| - [Rust will now release XZ compressed packages][rust-installer/57] | ||
| - [rustup will now prefer to download rust packages with | ||
| XZ compression][rustup/1100] over GZip packages. | ||
| - [Added the ability to escape `#` in rust documentation][41785] By adding |
This comment has been minimized.
This comment has been minimized.
mbrubeck
Jul 13, 2017
Contributor
This change is mentioned twice (once here, then again in "Compatibility Notes" below).
This comment has been minimized.
This comment has been minimized.
brson
Jul 13, 2017
Contributor
Yeah, I noticed that and decided that it's ok - it's a feature addition with compatibility concerns. shrug
This comment has been minimized.
This comment has been minimized.
|
@steveklabnik since we're reverting this change that affects nmake, at least temporarily, to give more time for the ecosystem to adapt, it might be worth mentioning in the release announcement so users are aware. |
Zoxc
reviewed
Jul 13, 2017
| - [From the pound escape, lines consisting of multiple `#`s are | ||
| now visible][41785] | ||
| - [`for` loop desugaring has changed such that `break` does not | ||
| affect type inference][42634] |
This comment has been minimized.
This comment has been minimized.
Zoxc
Jul 13, 2017
Contributor
This pull request is a fix for #42265 which has never been stable.
This should say: for loop desugaring has changed such that the iterator is not borrowed during the loop body.
#42265 should also be referenced.
It probably doesn't belong in compatibility notes since it should have no effect on Rust code.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
|
Oh, if the jobserver patch is reverted, it will need to be removed from the relnotes. |
This comment has been minimized.
This comment has been minimized.
|
@brson I'm not seeing any revert PR, was this mentioned somewhere? |
jimmycuadra
reviewed
Jul 14, 2017
| `aborting due to N previous errors`][42150] This was previously inaccurate and | ||
| would only count certain kinds of errors. | ||
| - [The compiler now supports Visual Studio 2017][42225] | ||
| - [The compiler is now be built against LLVM 4.0.1 by default][42948] |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
|
@jimmycuadra yeah, they are both pretty much the same, probably we should only keep the link to the private_in_public PR. |
added some commits
Jul 15, 2017
sfackler
reviewed
Jul 19, 2017
| command, which has been available since 1.16. | ||
| - [Ending a float literal with `._` is now a hard error. | ||
| Example: `42._` .][41946] | ||
| - [Any use of a private `extern crate` outside of it's module is now a |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
|
@bors p=100 needs to land before the release! |
steveklabnik
reviewed
Jul 19, 2017
| [RFC 1558]: https://github.com/rust-lang/rfcs/pull/1558 | ||
| [RFC 1624]: https://github.com/rust-lang/rfcs/pull/1624 | ||
| [RFC 1721]: https://github.com/rust-lang/rfcs/pull/1721 | ||
| [`Command::envs`]: https://doc.rust-lang.org/nightly/std/process/struct.Command.html#method.envs |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
|
@bors: r+ |
This comment has been minimized.
This comment has been minimized.
|
|
This comment has been minimized.
This comment has been minimized.
|
|
This comment has been minimized.
This comment has been minimized.
|
Github shows no conflict. Dunno whats up. @bors: retry maybe? |
This comment has been minimized.
This comment has been minimized.
|
This needs to be rebased, the conflict is presumably in a submodule. |
This comment has been minimized.
This comment has been minimized.
|
Closing in favour of a new PR without submodule problems. #43368 |
XAMPPRocky commentedJun 7, 2017
•
edited by brson
This is waiting on any beta backports in the coming weeks, and the lib stabilisations pr.
Rendered.