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
Rakudo parses "{ }\n&f" as a junction #2280
Comments
From @Kodiologistmy &f; # Yields: |
From @kylehaThis is an automatically generated mail to inform you that tests are now available in S04-statements/terminator.t commit 4cb303effa82269e2fc72f91ddeb800042d77da0 [S04-statements/terminator.t] Added a test for RT #79964. Inline Patchdiff --git a/S04-statements/terminator.t b/S04-statements/terminator.t
index cbc0edd..5238797 100644
--- a/S04-statements/terminator.t
+++ b/S04-statements/terminator.t
@@ -2,7 +2,7 @@ use v6;
use Test;
-plan 14;
+plan 15;
# L<S04/"Statement-ending blocks"/"will terminate a statement">
@@ -54,4 +54,8 @@ eval_dies_ok "42 if 23\nis 50; 1",
# not sure this belong here, suggestions for better places are welcome
eval_dies_ok '(1) { $foo = 2 }', 'parens do not eat spaces after them';
+# RT #79964
+#?rakudo todo 'RT #79964'
+eval_lives_ok "my &f;\nsub g() { }\n&f;", 'implicit terminator before & sigil';
+
# vim: ft=perl6 |
The RT System itself - Status changed from 'new' to 'open' |
From @jnthnOn Mon Nov 29 15:30:07 2010, KyleHa wrote:
Oops, the { } interpolates there. Fixed the test, which now passes thanks /jnthn |
@jnthn - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#79964 (status was 'resolved')
Searchable as RT79964$
The text was updated successfully, but these errors were encountered: