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
No-args 'print' and 'say' (without explicit parentheses) should generate a warning in Rakudo #1509
Comments
From @masak<masak> std: say STD generates a warning for these cases, but Rakudo doesn't. |
From @masak<masak> rakudo: say for 1..3 |
@coke - Status changed from 'new' to 'open' |
1 similar comment
@coke - Status changed from 'new' to 'open' |
From @cokeStill no errors or warnings in rakudo 88c5a5. -- |
From @FROGGSstd: say # that is what rakudo should do m: say # but it does not, which is a bug |
From @cokeOn Wed Aug 27 12:59:12 2014, FROGGS.de wrote:
rakudo now errors on both say AND say() instead of neither, but should only error on the former. A test was just added to S32-exceptions/misc.t in fd376fc, but there are older tests (that need review) in S16-io/bare-say.t -- |
From @cokeOn Fri Aug 29 06:36:12 2014, coke wrote:
Followup commits have this being caught at compile time, and tests were verified at the same time. Closing ticket. -- |
@coke - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#72844 (status was 'resolved')
Searchable as RT72844$
The text was updated successfully, but these errors were encountered: