-
-
Notifications
You must be signed in to change notification settings - Fork 372
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Some issue exposed by JSON::RPC #2684
Labels
ecosystem modules
regression
Issue did not exist previously
tests needed
Issue is generally resolved but tests were not written yet
Comments
AlexDaniel
added
regression
Issue did not exist previously
BLOCKER
Preventing the next release of rakudo, or just needing attention before the release
labels
Feb 8, 2019
Ah, obligatory ping, of course. @jnthn |
No change with jit or spesh disabled. |
Sticking |
Golf: Module.pm6 with:
And then:
|
jnthn
added a commit
to Raku/nqp
that referenced
this issue
Feb 12, 2019
When we compile some code to run it at BEGIN time, and a closure is taken and retained there, then it may have some connections to the faked-up lexical environment it was compiled in. In such cases, force lookups of lexicals to be late-bound, so that we do not get wrong indexes. Fixes the issue exposed in rakudo/rakudo#2684.
Tracked it down to a more general problem in the QAST compiler and fixed that; both the golfed example and the original module are happy now. |
jnthn
added
the
tests needed
Issue is generally resolved but tests were not written yet
label
Feb 12, 2019
AlexDaniel
removed
the
BLOCKER
Preventing the next release of rakudo, or just needing attention before the release
label
Feb 12, 2019
jnthn
added a commit
to Raku/nqp
that referenced
this issue
Feb 15, 2019
The previous approach fixed the bug, but was a bit too sweeping, leading to a large performance regression in some cases. With this fix (plus a Rakudo commit), rakudo/rakudo#2684 is still resolved, and the reported performance regression also eliminated.
jnthn
added a commit
that referenced
this issue
Feb 15, 2019
An earlier fix for #2684 was a bit too sweeping, and resulted in a performance regression. This fix deals more precisely with the cases known to be problematic. Includes a bump to NQP to get a QAST compiler that uses the new annotation.
Kaiepi
pushed a commit
to Kaiepi/rakudo
that referenced
this issue
Mar 7, 2019
An earlier fix for rakudo#2684 was a bit too sweeping, and resulted in a performance regression. This fix deals more precisely with the cases known to be problematic. Includes a bump to NQP to get a QAST compiler that uses the new annotation.
Kaiepi
pushed a commit
to Kaiepi/rakudo
that referenced
this issue
Mar 10, 2019
An earlier fix for rakudo#2684 was a bit too sweeping, and resulted in a performance regression. This fix deals more precisely with the cases known to be problematic. Includes a bump to NQP to get a QAST compiler that uses the new annotation.
Altai-man
added a commit
to Altai-man/roast
that referenced
this issue
May 20, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
ecosystem modules
regression
Issue did not exist previously
tests needed
Issue is generally resolved but tests were not written yet
See Raku/ecosystem-unbitrot#440.
JSON::RPC – Fail, Bisected: 8ef7c15
It is interesting:
The text was updated successfully, but these errors were encountered: