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
error message mentions parameter “$slip” (1.map: { Slip }) #4851
Comments
From @AlexDanielCode: Result: The problem is that it mentions some internal �$slip� parameter. In this simple case it is pretty clear what is happening, but imagine the |
From @LLFourn2¢ quick look: It just checks whether it's a Slip type but should also be checking that On Sat, Dec 12, 2015 at 2:30 PM Alex Jakimenko <perl6-bugs-followup@perl.org>
|
The RT System itself - Status changed from 'new' to 'open' |
From @geekosaurOn Fri, Dec 11, 2015 at 11:55 PM, Lloyd Fournier <lloyd.fourn@gmail.com>
It's not mapping over Slips in general; it's mapping over an *undefined* -- |
From @LLFournyep by Slip type I meant a Slip type object ie undefined Slip (as opposed I don't really understand why it should be an error or warning. 1.map: { Any } # ((Any)) On Sat, Dec 12, 2015 at 4:00 PM Brandon Allbery <allbery.b@gmail.com> wrote:
|
From @LLFourntest: On Sat, Dec 12, 2015 at 8:13 PM Elizabeth Mattijsen <liz@dijkmat.nl> wrote:
|
From @AlexDanielThis was fixed in rakudo/rakudo@502b886 Not sure why it's still not closed. Closing. On 2015-12-12 20:45:06, lloyd.fourn@gmail.com wrote:
|
@AlexDaniel - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#126883 (status was 'resolved')
Searchable as RT126883$
The text was updated successfully, but these errors were encountered: