[perl #131919] [RFC] Returning Failure from failed P6-level .parse

[Aleks-Daniel Jakimenko-Aleksejev via RT]

It was removed completely for 2017.08 release.

Rakudo commit:
https://github.com/rakudo/rakudo/commit/465d91abdfda038cb7feda35f7966be4ec39acf3
Discussion: https://irclog.perlgeek.de/perl6-dev/2017-08-21#i_15048995
On 2017-08-19 15:31:01, alex.jakime...@gmail.com wrote:
> I had to revert one of the nqp commits related to .parse:
> https://github.com/perl6/nqp/commit/d4d77b66c46c57de800b147df61fe486b4486acd
>
> Here's a ticket for the module that was affected by the change:
> https://github.com/p6-css/CSS-Module-p6/issues/10
>
> Most certainly we want this change back ASAP, but it had to be
> reverted for the
> release.
>
> ♥
>
> On 2017-08-19 05:36:36, alex.jakime...@gmail.com wrote:
> > 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.