diff options
| author | bors <bors@rust-lang.org> | 2018-06-16 13:08:16 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2018-06-16 13:08:16 +0000 |
| commit | 253205658edc477a0b429f3ce25a92099dc7ddc4 (patch) | |
| tree | 53ea6e46fd3c115ca933e2b370f158bb04154da3 | |
| parent | 61ba0180933485cf8a2bc6b7230a4c70b82bb063 (diff) | |
| parent | b676b37988e944cdae029a3d49c1ac3b246ab3fc (diff) | |
| download | rust-253205658edc477a0b429f3ce25a92099dc7ddc4.tar.gz rust-253205658edc477a0b429f3ce25a92099dc7ddc4.zip | |
Auto merge of #51591 - pietroalbini:release-notes-fix, r=Mark-Simulacrum
Remove `?` macro separator compatibility note from 1.27 release notes The implementation has been reverted in https://github.com/rust-lang/rust/pull/51417, so this no longer applies to 1.27.0. r? @Mark-Simulacrum
| -rw-r--r-- | RELEASES.md | 7 |
1 files changed, 0 insertions, 7 deletions
diff --git a/RELEASES.md b/RELEASES.md index 0fafe95d2c4..9c501dc05dc 100644 --- a/RELEASES.md +++ b/RELEASES.md @@ -92,13 +92,6 @@ Compatibility Notes will only print the inner type.][48553] e.g. `print!("{:?}", AtomicBool::new(true))` will print `true` not `AtomicBool(true)`. -- [`?` can no longer be a separator in macros.][49719] e.g. the following will - no longer compile. - ```rust - macro_rules! barplus { - ($(a)?+) => {} - } - ``` - [The maximum number for `repr(align(N))` is now 2²⁹.][50378] Previously you could enter higher numbers but they were not supported by LLVM. Up to 512MB alignment should cover all use cases. |