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
Num doesn't have a Range coercer #3737
Comments
From @Tux$ p6 -e'int.Range.say' $ p6 -e'my int $i = int.Range.max; $i.say' $ p6 -e'Inf.WHAT.say' -- |
From @masakI see two things in this ticket. Correct me if I'm wrong.
First thing: Num doesn't have a Range coercer.
Second thing: can't put Inf in Int, which is a dupe of https://rt.perl.org/Ticket/Display.html?id=61602, which is currently blocking on Raku/old-design-docs#27 but the last word on which is http://irclog.perlgeek.de/perl6/2014-08-20#i_9217322, IMO. So, mind if I change the name of this ticket to "Num doesn't have a Range coercer"? :) |
The RT System itself - Status changed from 'new' to 'open' |
From @TuxOn Thu, 19 Mar 2015 12:02:36 -0700, "Carl Mäsak via RT"
In which case Int.Range.max should not return Inf IMHO. Maybe it should
That, at the moment, is beyond my current level of understanding the
Is ok. -- |
From @masakTux (>>>), masak (>>), Tux (>):
Oh, no, you got me diametrically wrong. I identified two separate bug reports in your ticket, the second of which is that the Inf value cannot be put in an Int container. It *should* totally be possible, at least by current synopsis/TimToady/community consensus. But it isn't yet. What I identified as your "Second thing" was simply this discrepancy.
Renaming. |
From @cokeOn Mon Mar 16 05:01:38 2015, hmbrand wrote:
15:37 < [Coke]> m: Int.Range.say; Num.Range.say; So, this exists now... but it's broken in GLR. -- |
From @ninerThis seems to have been fixed in the meantime. Num.Range.say prints -Inf..Inf |
@niner - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#124082 (status was 'resolved')
Searchable as RT124082$
The text was updated successfully, but these errors were encountered: