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
callframe.perl message is LTA #2150
Comments
From @bbkr[17:43] <bbkr> rakudo: callframe.perl # known_and_NYI or should I report it as [17:44] <pmichaud> bbkr: it's TODO [17:52] <moritz_> adding a method perl() { fail "Can't serialize callframes" } [17:52] <bbkr> pmichaud: because "callframe.WHAT" is "CallFrame" [17:53] <pmichaud> then callframe.perl should work [17:54] <pmichaud> okay, I'll accept that the error message is wrong here. |
From @bbkr[17:57] <pmichaud> why are we getting a ParrotInterpret...... oh, I see |
The RT System itself - Status changed from 'new' to 'open' |
From @cokeOn Thu Sep 09 08:57:52 2010, pawel.pabian@implix.com wrote:
Now generates something that is probably reasonable: 02:48 <[Coke]> rakudo: callframe.WHAT.say Closable with tests. -- |
From @usev6skids++ added a (passing) test to S06-advanced/callframe.t with commit Raku/roast@92b416ca8b I'm closing this ticket now. |
1 similar comment
From @usev6skids++ added a (passing) test to S06-advanced/callframe.t with commit Raku/roast@92b416ca8b I'm closing this ticket now. |
@usev6 - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#77752 (status was 'resolved')
Searchable as RT77752$
The text was updated successfully, but these errors were encountered: