bjoernager/rust
bjoernager/rust
1
Fork 0
Code Activity

Remove ? macro separator compatibility note from 1.27 release notes

Browse source 
The implementation has been reverted.
This commit is contained in:
Pietro Albini 2018-06-16 13:39:35 +02:00
parent a385095f9a
commit b676b37988
No known key found for this signature in database
GPG key ID: E8C1042DD1624519
1 changed files with 0 additions and 7 deletions
Download patch file Download diff file Expand all files Collapse all files

7
RELEASES.md
View file

@ -92,13 +92,6 @@ Compatibility Notes
will only print the inner type.][48553] e.g. will only print the inner type.][48553] e.g.
`print!("{:?}", AtomicBool::new(true))` will print `true` `print!("{:?}", AtomicBool::new(true))` will print `true`
not `AtomicBool(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 - [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 could enter higher numbers but they were not supported by LLVM. Up to 512MB
alignment should cover all use cases. alignment should cover all use cases.