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
Crash in Junction:D.BUILDALL This type (Scalar) does not support elems
#6308
Comments
From @zoffixznetWhile chasing some other bugs, came across this one: <Zoffix__> m: Junction.new.BUILDALL: {} Not sure how much it matters in itself, but figured I'd report it, in case it's a symptom of a bigger bug. |
From @smlsOn Fri, 02 Jun 2017 18:58:22 -0700, cpan@zoffix.com wrote:
This can be golfed to just: Junction.new; And it has been fixed to throw a better error message now: ➜ Junction.new; According to bisectable¹, it was fixed by a commit² in June. The 'bigger issue' was possibly RT #131395. Is `Junction.new` meant to be public API? [1] https://gist.github.com/Whateverable/13556140482322fd5bf4080092a1d284 |
The RT System itself - Status changed from 'new' to 'open' |
From @zoffixznetOn Sat, 30 Sep 2017 12:28:48 -0700, smls75@gmail.com wrote:
Don't see a reason why not.
If it weren't, all fixed bugs still need a test to cover them. If the test should
|
From @smlsOn Sat, 30 Sep 2017 13:13:31 -0700, cpan@zoffix.com wrote:
Well, passing a 'type' string parameter to select between what is essentially different object sub-types, seems internal-ish. I can't think of anything else in the public Perl 6 API which does this; a more Perl 6'ish API would dispatch based on *different* named parameters, or simply make the object sub-types available as separate subclasses. So it might make sense to consider `Junction.new` as "not public API" for now, until this is ironed out.
Noted; Marking the ticket as TESTNEEDED. A test for the current behavior could look like: use Test; |
From @zoffixznetTests: Raku/roast@5ebf6f9303 |
@zoffixznet - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#131490 (status was 'resolved')
Searchable as RT131490$
The text was updated successfully, but these errors were encountered: