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
Custom infix:<~~> multi not used by rakudo #4453
Comments
From @ShimmerFairy<ShimmerFairy> m: class Foo { }; multi sub infix:< To explain, the ~~ infix is one of those operators that src/Perl6/Actions.pm treats specially, in this case constructing an AST for the expression with the 'make_smartmatch' method. The QAST generated by this method bypasses the infix and uses the ACCEPTS method on the arguments, meaning definitions of infix:< Bug #81336 may also be caused by this special treatment, since the generated QAST (as mentioned) gives no consideration to any defined infix:<~~> functions and shortcuts to calling ACCEPTS on the left-hand side. |
From @moritzHi, On 04.08.2015 00:52, Faye (via RT) wrote:
I'd argue that it's permissible to not consider custom infix:<~~>, Also note that the standard infix:<~~> cannot be a normal operator, So, not a bug. (But I cannot reject it in rt.perl.org right now because of login Cheers, |
The RT System itself - Status changed from 'new' to 'open' |
@moritz - Status changed from 'open' to 'rejected' |
From @labsterI'm actually going to reopen this one, because I think it needs the same treatment as #125427 -- an error message that you're doing something which will never work. See commit 792578840. On Mon Aug 03 23:50:07 2015, moritz wrote:
|
@labster - Status changed from 'rejected' to 'open' |
From @usev6I created a PR for rakudo (following RT #125427): rakudo/rakudo#487 $ perl6-m -e 'class Foo { }; multi sub infix:< |
1 similar comment
From @usev6I created a PR for rakudo (following RT #125427): rakudo/rakudo#487 $ perl6-m -e 'class Foo { }; multi sub infix:< |
From @lizmatMerged.
|
From @usev6I added a test with commit d2d4f7a9. In comments to PR 487 it was suggested to make the error message even better by mentioning .ACCEPTS (rakudo/rakudo#487 (comment)). Should we leave the ticket open until someone does that or is the ticket closeable? |
1 similar comment
From @usev6I added a test with commit d2d4f7a9. In comments to PR 487 it was suggested to make the error message even better by mentioning .ACCEPTS (rakudo/rakudo#487 (comment)). Should we leave the ticket open until someone does that or is the ticket closeable? |
From @jnthnOn Fri Aug 14 13:30:13 2015, bartolin@gmx.de wrote:
Did the hint: $ perl6-m -e "class Foo { }; multi sub infix:< So categorically closable now. :-) |
@jnthn - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#125745 (status was 'resolved')
Searchable as RT125745$
The text was updated successfully, but these errors were encountered: