Perl 6 - the future is here, just unevenly distributed

IRC log for #perl6-release, 2016-01-28

| Channels | #perl6-release index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
00:09 edehont joined #perl6-release
00:12 edehont joined #perl6-release
00:12 edehont_ joined #perl6-release
00:12 edehont joined #perl6-release
06:23 _Gustaf_ joined #perl6-release
08:03 FROGGS joined #perl6-release
11:42 edehont joined #perl6-release
15:07 lizmat joined #perl6-release
15:11 lizmat joined #perl6-release
15:11 b2gills It would be nice if the new Rakudo * didn't backslide on ï½¢().permutationsï½£ and ï½¢(1).permutationsï½£
15:11 b2gills see: https://github.com/rakudo/rakudo/pull/686 which also fixes ï½¢+permuations(0)ï½£ to correctly return 1 ( ï½¢permuations(n) == n!ï½£ ) https://www.wolframalpha.com/input/?i=number+of+permutations+of+0+elements
15:12 lizmat b2gills: until we know how we're going to handle these fixes, I'm not going to merge these PR's
15:13 b2gills So 6.c is always going to be broken?
15:13 jnthn What does "backslide" in this case mean?
15:14 jnthn That we regressed it *since* 2015.12?
15:14 b2gills It regressed since the previous Rakudo * (2015.12 is broken)
15:14 jnthn Ah
15:14 jnthn OK, then it waits as lizmat said.
15:15 jnthn Not least 'cus we basically have something ready to cut for 2016.01
15:15 b2gills (1).permutations is supposed to work but a speed fix broke it because ROAST doesn't test it
15:16 jnthn :(
15:17 jnthn Not sure why we were doing speed "fixes" in 2015.12 really...not a particularly good risk assessment.
15:17 jnthn Anyway, we can cover it in 6.c.1 or so
15:18 jnthn We'll look at it more next week; I'm too tied up with other things this week...
15:18 lizmat jnthn: it just goes to show that roast is maybe covering 10-20% of the spec
15:18 b2gills I have a ROAST patch (linked) as well that should at least go in 6.d to test both cases
15:19 b2gills once it gets fixed of course, because it doesn't do the skip thing
15:19 lizmat feels to me that saying "6.c" is what is covered by roast at that time, is allowing for a lot of code deviance
15:20 jnthn lizmat: It's still probably the least imperfect option. :)
15:20 jnthn And over time, roast will tighten.
15:20 b2gills I just really dislike that a math major may try ï½¢permutations(0|1) == 1ï½£ and wonder why it is a failure
15:21 jnthn b2gills: I'd not worry too much about people experimenting lightly and hitting that forevermore; without a version declaration we'll default to latest and greatest, and people who're just having a play surely won't be writing a version decl. :)
15:21 * lizmat refrains from getting into another version rant
15:22 jnthn hah :)
15:23 jnthn Yes, not worth it until there's a more precisely defined strategy doc to rant about.
15:23 jnthn And perhaps not even then. :P
15:23 b2gills I understand the position of don't fix things that aren't tested to some extent.
15:24 jnthn b2gills: Give us another week or so to get our "how we're handling changes going forward" stuff at least somewhat worked out enough to move forward with things, and we'll get your PRs in, in the fitting way.
15:25 b2gills Fair enough
15:27 [Coke] For now, the goal is getting the bare minimum out so we can do an R*
15:27 [Coke] ... ok. I'm at dayjob now, but will get the compiler release done before midnight eastern.
15:32 jnthn [Coke]++
15:32 jnthn OH, that means I should cut a Moar
15:32 jnthn I can probably do that before midnight CET, which is earlier ;)
15:57 cognominal joined #perl6-release
17:39 FROGGS joined #perl6-release
20:44 lizmat joined #perl6-release
22:24 FROGGS joined #perl6-release

| Channels | #perl6-release index | Today | | Search | Google Search | Plain-Text | summary