The change was moved to v6.d in this commit: https://github.com/rakudo/rakudo/commit/d2278b471cb0bd691dc7a1235fbcb9318ff5d61f
On 2017-08-17 08:50:48, alex.jakime...@gmail.com wrote: > See this commit: > https://github.com/rakudo/rakudo/commit/9501edae4f73a970e3270e3b0336a7b3045d3329 > > These roast commits: > * > https://github.com/perl6/roast/commit/1fb68c4b7a7c975f26fc81ad79f000958d1b4afd > * > https://github.com/perl6/roast/commit/b53616f8e67f9b19366008b3abf55400a3d6cd2b > > And this justification: > * https://irclog.perlgeek.de/perl6-dev/2017-08-16#i_15021994 > > This blog post noticing the breakage due to the change: > * https://gfldex.wordpress.com/2017/08/17/parsing-nothing/ > > And these thoughts about postponing it to v6.d: > * https://irclog.perlgeek.de/perl6-dev/2017-08-17#i_15032160 > > > I am confident that we will not be able to process this change and all > potential breakage associated with it in ≈3 days before the release, > so the revert is coming. > > Personally, I don't mind rereverting it afterwards for inclusion in > 2017.09, assuming we make sure to fix all modules that were relying on > Nils being returned. However, I do see the point for postponing it > till v6.d. > > > So should we feel adventurous and push this change as early as we can > (in 2017.09, aftear at least one month)? Or is it better to be safe > and wait for v6.d? Please discuss.
