Really breaking changes are rare and broadly announced, so I'm not really sure this is necessary. Packages are much more wild about making changes that will break your code than the core language is – which is as it should be.
On Tue, Feb 25, 2014 at 11:21 AM, <a...@10xtechnologies.com> wrote: > Met John Myles White the other day and he mentioned an upcoming breaking > change in array view behavior, which I also just saw referenced in #5949. > What do you guys think about putting together a page that tracks potential > and likely breaking changes? It could really just be a list of GitHub issue > #'s. What I'd like to do for our internal use is make a set of simple unit > tests around each of these potential changes so it's crystal clear when > these changes actually take place. >
