The [breaking] tag in GitHub is just what I was looking for, thanks for pointing it out.
Which is the issue for the array slicing going from copy to reference? I think that's the change JWM mentioned. On Tuesday, February 25, 2014 8:30:21 AM UTC-8, Tim Holy wrote: > > If you visit the issues page and click on "breaking" in the labels on the > left, you'll get the whole list. If there is a breaking change that hasn't > had > that label applied, please file an issue. But I don't think a separate web > page > would be any easier to keep in sync (to the contrary). > > Specifically regarding, #5949, it's _way_ too early to make any kind of > preparations whatsoever. The whole point of the issue is to be a > target---from > users as well as developers---for both rotten tomatoes and pink ponies. > We'll > see which we get more of; I'm quite curious to know what the reaction will > be. > > --Tim > > On Tuesday, February 25, 2014 08:21:07 AM > al...@10xtechnologies.com<javascript:>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. >
