-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
Revert abort on unwinding through FFI on stable #58795
Merged
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -4,10 +4,10 @@ Version 1.33.0 (2019-02-28) | |
Language | ||
-------- | ||
- [You can now use the `cfg(target_vendor)` attribute.][57465] E.g. | ||
`#[cfg(target_vendor="linux")] fn main() { println!("Hello Linux!"); }` | ||
`#[cfg(target_vendor="apple")] fn main() { println!("Hello Apple!"); }` | ||
- [Integer patterns such as in a match expression can now be exhaustive.][56362] | ||
E.g. You can have match statement on a `u8` that covers `0..=255` and | ||
you would no longer be required to have a `_ => unreachable!()` case. | ||
you would no longer be required to have a `_ => unreachable!()` case. | ||
- [You can now have multiple patterns in `if let` and `while let` | ||
expressions.][57532] You can do this with the same syntax as a `match` | ||
expression. E.g. | ||
|
@@ -51,8 +51,7 @@ Language | |
// Allowed as there is only one `Read` in the module. | ||
pub trait Read {} | ||
``` | ||
- [`extern` functions will now abort by default when panicking.][55982] | ||
This was previously undefined behaviour. | ||
- [You may now use `Rc`, `Arc`, and `Pin` as method receivers][56805]. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. what's up with this? just an orthogonal change? |
||
|
||
Compiler | ||
-------- | ||
|
@@ -109,27 +108,30 @@ Compatibility Notes | |
are now deprecated in the standard library, and their usage will now produce a warning. | ||
Please use the `str::{trim_start, trim_end, trim_start_matches, trim_end_matches}` | ||
methods instead. | ||
- The `Error::cause` method has been deprecated in favor of `Error::source` which supports | ||
downcasting. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. (similar) |
||
|
||
[57615]: https://github.com/rust-lang/rust/pull/57615/ | ||
[57465]: https://github.com/rust-lang/rust/pull/57465/ | ||
[57532]: https://github.com/rust-lang/rust/pull/57532/ | ||
[57535]: https://github.com/rust-lang/rust/pull/57535/ | ||
[57566]: https://github.com/rust-lang/rust/pull/57566/ | ||
[55982]: https://github.com/rust-lang/rust/pull/55982/ | ||
[56303]: https://github.com/rust-lang/rust/pull/56303/ | ||
[56351]: https://github.com/rust-lang/rust/pull/56351/ | ||
[56362]: https://github.com/rust-lang/rust/pull/56362 | ||
[56642]: https://github.com/rust-lang/rust/pull/56642/ | ||
[56769]: https://github.com/rust-lang/rust/pull/56769/ | ||
[56805]: https://github.com/rust-lang/rust/pull/56805 | ||
[56947]: https://github.com/rust-lang/rust/pull/56947/ | ||
[57049]: https://github.com/rust-lang/rust/pull/57049/ | ||
[57067]: https://github.com/rust-lang/rust/pull/57067/ | ||
[57105]: https://github.com/rust-lang/rust/pull/57105 | ||
[57130]: https://github.com/rust-lang/rust/pull/57130/ | ||
[57167]: https://github.com/rust-lang/rust/pull/57167/ | ||
[57175]: https://github.com/rust-lang/rust/pull/57175/ | ||
[57234]: https://github.com/rust-lang/rust/pull/57234/ | ||
[57332]: https://github.com/rust-lang/rust/pull/57332/ | ||
[56947]: https://github.com/rust-lang/rust/pull/56947/ | ||
[57049]: https://github.com/rust-lang/rust/pull/57049/ | ||
[57067]: https://github.com/rust-lang/rust/pull/57067/ | ||
[56769]: https://github.com/rust-lang/rust/pull/56769/ | ||
[56642]: https://github.com/rust-lang/rust/pull/56642/ | ||
[56303]: https://github.com/rust-lang/rust/pull/56303/ | ||
[56351]: https://github.com/rust-lang/rust/pull/56351/ | ||
[55982]: https://github.com/rust-lang/rust/pull/55982/ | ||
[56362]: https://github.com/rust-lang/rust/pull/56362 | ||
[57105]: https://github.com/rust-lang/rust/pull/57105 | ||
[57465]: https://github.com/rust-lang/rust/pull/57465/ | ||
[57532]: https://github.com/rust-lang/rust/pull/57532/ | ||
[57535]: https://github.com/rust-lang/rust/pull/57535/ | ||
[57566]: https://github.com/rust-lang/rust/pull/57566/ | ||
[57615]: https://github.com/rust-lang/rust/pull/57615/ | ||
[cargo/6484]: https://github.com/rust-lang/cargo/pull/6484/ | ||
[`unix::FileExt::read_exact_at`]: https://doc.rust-lang.org/std/os/unix/fs/trait.FileExt.html#method.read_exact_at | ||
[`unix::FileExt::write_all_at`]: https://doc.rust-lang.org/std/os/unix/fs/trait.FileExt.html#method.write_all_at | ||
|
@@ -170,7 +172,7 @@ Language | |
- [You can now match against literals in macros with the `literal` | ||
specifier.][56072] This will match against a literal of any type. | ||
E.g. `1`, `'A'`, `"Hello World"` | ||
- [Self can now be used as a constructor and pattern for unit and tuple structs.][56365] E.g. | ||
- [Self can now be used as a constructor and pattern for unit and tuple structs.][56365] E.g. | ||
```rust | ||
struct Point(i32, i32); | ||
|
||
|
@@ -460,7 +462,7 @@ Version 1.31.0 (2018-12-06) | |
|
||
Language | ||
-------- | ||
- 🎉 [This version marks the release of the 2018 edition of Rust.][54057] 🎉 | ||
- 🎉 [This version marks the release of the 2018 edition of Rust.][54057] 🎉 | ||
- [New lifetime elision rules now allow for eliding lifetimes in functions and | ||
impl headers.][54778] E.g. `impl<'a> Reader for BufReader<'a> {}` can now be | ||
`impl Reader for BufReader<'_> {}`. Lifetimes are still required to be defined | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
Looks like more spurious changes? Shouldn't this (have been) fixed before approving...?
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 was intentional (note the separate commit); we wanted to land some additional release notes and since we were merging this into stable combined it into one.
In hindsight, I should've mentioned this in the PR description.