# New Ticket Created by "Carl Mäsak" # Please include the string: [perl #72554] # in the subject line of all future correspondence about this issue. # <URL: http://rt.perl.org/rt3/Ticket/Display.html?id=72554 >
<colomon> ooo, obsolete bit on Num in S02: "One consequence of all this is that you may no longer write a Num as 42. with just a trailing dot. You must instead say either 42 or 42.0." 42.0 isn't a Num anymore... <masak> no? <masak> rakudo: say 42.0.WHAT <p6eval> rakudo 1d4928: OUTPUT«Num()» <jnthn> ng: say 42.0.WHAT <p6eval> ng 8aa3b7: OUTPUT«Rat()» <masak> but Rat ~~ Num, no? <masak> rakudo: say Rat ~~ Num <p6eval> rakudo 1d4928: OUTPUT«0» <masak> o_O <masak> rakudo: say Int ~~ Num <p6eval> rakudo 1d4928: OUTPUT«1» <jnthn> masak: Numeric <pmurias> ng: say Rat ~~ Num <p6eval> ng 8aa3b7: OUTPUT«0» <masak> tell me the logic of Int being a Num but Rat not being a Num. <jnthn> masak: I'm not sure if Int ~~ Num should be true any more. <masak> rakudo: Numeric <p6eval> rakudo 1d4928: OUTPUT«Could not find non-existent sub Numericin Main (file src/gen_setting.pm, line 324)» <pmurias> Rat can hold values which Num can't <jnthn> So can Int. :-) * masak submits a very confused rakudobug <pmurias> jnthn: so one could argue it shouldn't ~~ Num <colomon> It definitely shouldn't, IMO. <colomon> they're all Numeric. <colomon> that's the real relationship that's interesting. <colomon> anything else is asking for trouble. <jnthn> pmurias: My understanding is what colomon just said. <jnthn> pmurias: Some tests will need updating and stuff though <jnthn> colomon: We should probably try and do that in ng. <jnthn> colomon: It shouldn't be *too* hard. As far as I'm concerned this bug can be closed when (Int ~~ Num) and (Rat ~~ Num) yield the same result. :-)
