summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAlex Crichton <alex@alexcrichton.com>2016-02-29 10:42:03 -0800
committerAlex Crichton <alex@alexcrichton.com>2016-02-29 10:42:03 -0800
commita5d1e7a59a2a3413c377b003075349f854304b5e (patch)
treed334e97292c54691db22573cdb670d18e4f473c0
parent712f76f4e9ec2bc581408db7021230728b4dcad4 (diff)
parent35dc0169e2b707f4382a66627a072b2d6dac1c8b (diff)
Merge pull request #31974 from brson/beta-next1.7.0
Move the RFC 1214 breakage to 1.7 compatibility notes
-rw-r--r--RELEASES.md16
1 files changed, 6 insertions, 10 deletions
diff --git a/RELEASES.md b/RELEASES.md
index 1b0b9aa6069..37a11580403 100644
--- a/RELEASES.md
+++ b/RELEASES.md
@@ -1,16 +1,6 @@
Version 1.7.0 (2016-03-03)
==========================
-Language
---------
-
-* Soundness fixes to the interactions between associated types and
- lifetimes, specified in [RFC 1214], [now generate errors][1.7sf] for
- code that violates the new rules. This is a significant change that
- is known to break existing code, so it has emitted warnings for the
- new error cases since 1.4 to give crate authors time to adapt. The
- details of what is changing are subtle; read the RFC for more.
-
Libraries
---------
@@ -112,6 +102,12 @@ Cargo
Compatibility Notes
-------------------
+* Soundness fixes to the interactions between associated types and
+ lifetimes, specified in [RFC 1214], [now generate errors][1.7sf] for
+ code that violates the new rules. This is a significant change that
+ is known to break existing code, so it has emitted warnings for the
+ new error cases since 1.4 to give crate authors time to adapt. The
+ details of what is changing are subtle; read the RFC for more.
* [Several bugs in the compiler's visibility calculations were
fixed][1.7v]. Since this was found to break significant amounts of
code, the new errors will be emitted as warnings for several release