On Sat Jul 09 07:13:48 2016, jn...@jnthn.net wrote: > On Tue Jul 05 17:51:46 2016, ug...@cpan.org wrote: > > Note that the final decode-base64 candidate shows the correct results > > when debugging statements are added > > > > This gist also shows a small change that makes it produce the correct > > values but it still segfaults more often than not > > https://gist.github.com/ugexe/baa168a641894a0731595c812724f76d > > Having dug into it a little, I'm not sure that the new multi-caching > stuff has caused this, so much as uncovered it (perhaps by moving GC > collection points
You are right. I golfed it down to the following gist which does not use multi methods: https://gist.github.com/ugexe/7ce08d3ad4cfd36f275c437ba9713471 In the gist comments there is also a link to the bisect output, but for brevity: bisect output: https://gist.github.com/Whateverable/e0a28162b19f601616aa8776f24dd027 rakudo commit: https://github.com/rakudo/rakudo/commit/5581b24
