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
Something funny with modifying a subset where part of the check is calling a method on the item #5092
Comments
From @jonathanstowe perl6 -e 'subset JJ where *.can("foo"); -> JJ:D $a { } ' This does not happen without the Type modifier in the signature, i.e. subset JJ where *.can("foo"); -> JJ $a { } But a modified subset that does not call a method is fine: subset JJ where { True }; -> JJ:D $a { } But it appears that in fact that it isn't 'can' that is the culprit but using *any* method on the item: perl6 -e 'subset JJ where *.foo; -> JJ:D $a { } ' |
From @jonathanstoweMethod 'iterator' must be implemented by Iterable because it is required by a role |
From @jnthnOn Wed Jan 27 12:12:17 2016, jns+bc@gellyfish.co.uk wrote:
We were mishandling the Subtype:D case in general, and sometimes it just didn't go quite so badly as other times. I've hopefully fixed that now, and added some tests in S12-subset/subtypes.t. |
The RT System itself - Status changed from 'new' to 'open' |
@jnthn - Status changed from 'open' to 'resolved' |
From 1parrota@gmail.comjnthn's been working really hard. On 7/21/16, jnthn@jnthn.net via RT <perl6-bugs-followup@perl.org> wrote:
|
Migrated from rt.perl.org#127394 (status was 'resolved')
Searchable as RT127394$
The text was updated successfully, but these errors were encountered: