about summary refs log tree commit diff
diff options
context:
space:
mode:
authorPietro Albini <pietro@pietroalbini.org>2018-06-16 13:39:35 +0200
committerPietro Albini <pietro@pietroalbini.org>2018-06-16 13:39:35 +0200
commitb676b37988e944cdae029a3d49c1ac3b246ab3fc (patch)
treee53809e5a947353e0c8e8fcd54564292432935cf
parenta385095f9a6d4d068102b6c72fbdc86ac2667e51 (diff)
downloadrust-b676b37988e944cdae029a3d49c1ac3b246ab3fc.tar.gz
rust-b676b37988e944cdae029a3d49c1ac3b246ab3fc.zip
Remove `?` macro separator compatibility note from 1.27 release notes
The implementation has been reverted.
-rw-r--r--RELEASES.md7
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.