| MasterDuke | .tell jnthn if it helps, here's the MVM_dump_backtrace output at the problematic coerce_ni when running `say(100000000000000009)` gist.github.com/MasterDuke17/a34c6...a67f0249db | 00:53 | |
| yoleaux | MasterDuke: I'll pass your message to jnthn. | ||
| MasterDuke | .tell timotimo if it helps, here's the MVM_dump_backtrace output at the problematic coerce_ni when running `say(100000000000000009)` gist.github.com/MasterDuke17/a34c6...a67f0249db | ||
| yoleaux | MasterDuke: I'll pass your message to timotimo. | ||
| ugexe | zef is suddently failing its appveyor tests when using an absolute path ala `zef install C:\my\repo` | 02:31 | |
| must be github.com/rakudo/rakudo/commit/49...e206340de4 somehow | 02:44 | ||
| samcv | i'm deciding on the heirarchy of unicode property values right now | 02:55 | |
| we will have General_Category and Script for sure. then if we add Grapheme_Cluster_Break that cuts the number of property values with conflicts down to 30 | |||
| if anybody wants to see, github.com/perl6/specs/issues/118#...-302968322 the conflicts before resolving General_Category and Script | 02:56 | ||
| and thinking we should resolve Numeric_Type as well. since i'm sure code that does <:Numeric> exists out there. and Numeric is a value of Numeric_Type | 02:57 | ||
| ugexe | m: say $*CWD.parts; # regression? | 03:08 | |
| camelia | Map.new((:basename("camelia"),:dirname("/home"),:volume(""))) | ||
| ugexe | star: say $*CWD.parts | 03:09 | |
| camelia | {basename => star-2016.10, directory => /home/camelia, dirname => /home/camelia, volume => } | ||
| samcv | it's going to get more fun now i'm going to add in Property Names as well and how they interact with property aliases | 03:11 | |
| ugexe | Zoffix: ^ note the above... it switched to a Map but more importantly it does not include the "directory" key | 03:18 | |
| MasterDuke | ugexe: i believe the change to Map was intentional, to make it immutable. don't know about the "directory" key though | 03:20 | |
| ugexe | whatever the problem is causing zef to fail was introduced in the last 13 hours anyway | 03:26 | |
| zef to fail on *windows* | 03:27 | ||
| "This type cannot unbox to a native string: P6opaque, Zef::Utils::URI::URI::File" | 03:37 | ||
| AlexDaniel | samcv: by the way, um… | 03:39 | |
| samcv: why not simply error out on stuff that is ambiguous? | 03:40 | ||
| samcv | that is fair enough. but i don't want to break everybodies code | 03:41 | |
| so i cannot do such a thing for 6.c | |||
| there at least needs to be some heirachy when i retrofit our unicode system for me to not have conflicts and also make sure .unimatch and other random assortted things work properly :> | |||
| sadly it is not that simple from 1. breaking code and 2. how things are already setup inside MoarVM rakudo/nqp etc | 03:42 | ||
| but i'm down for only "Guaranteeing" certain properties which could be a different list | 03:43 | ||
| but even if we don't guarantee certain things i need to at least make some heirarchy. | |||
| ugexe | Zoffix: error seems to be a change in coercion. $*SPEC.join($foo, $bar, $baz) - if $foo is a match object it no longer gets stringified (hence the unbox error above) | 03:44 | |
| Zoffix | .parts is not a regression | 06:53 | |
| ugexe: are you using $*SPEC.join directly? | 06:54 | ||
| Ah ok, you already committed a patch | 06:57 | ||
| ZOFVM: Files=1242, Tests=135655, 112 wallclock secs (21.74 usr 3.25 sys + 2293.68 cusr 157.36 csys = 2476.03 CPU) | 07:05 | ||
| Geth | rakudo/nom: 232cf190d6 | (Zoffix Znet)++ | src/core/IO/Spec/Win32.pm Add Str type constraints to IO::Spec::Win32 .join and .catpath |
07:06 | |
| Zoffix | ZOFFLOP: t/spec/S17-supply/interval.t | 07:23 | |
| I need to adjust one 6.c-errata test that I'm arguing is incorrect: github.com/perl6/roast/blob/6.c-er....t#L84-L88 | 07:25 | ||
| 1) It expects different output for @array than for $array | |||
| 2) This is due to the signature in IO::Handle.print being *@, while in IO::Handle.say (and with my patch in .put) and &say, &put, and &print it's **@ | 07:26 | ||
| 3) It appears the test was merely covering the current, at the time, behaviour. I don't recognize this person and they do not appear to be a member of rakudo org: github.com/perl6/roast/commit/d663...6b88fabefb | 07:28 | ||
| ZofBot: the milk stool is complete! | 07:29 | ||
| ZofBot | Zoffix, A call to the scalar version "$o | ||
| nine | ZofBot: FWIW zhuomingliang is more of a MoarVM developer | 07:41 | |
| ZofBot | nine, substr($ | ||
| nine | Zoffix: FWIW zhuomingliang is more of a MoarVM developer | ||
| Zoffix | noted | ||
| Geth | rakudo/nom: 613bdcf834 | (Zoffix Znet)++ | src/core/IO/Handle.pm [io grant] Make IO::Handle.print/.put sig consistent ... with IO::Handle.say, &say, &print, and &put |
07:42 | |
| roast: 050d718a1d | (Zoffix Znet)++ | S16-io/print.t Fix incorrect IO::Handle.print: @array 1) It expects different output for @array than for $array 2) This is due to the signature in IO::Handle.print being *@, while in IO::Handle.say (and with my patch in .put) and &say, &put, and &print it's **@ 3) Looking at the commit that brought the test, it appears the test was merely covering the current, at the time, behaviour, rather than a product of conscious design decision to make behaviour different from subroutine forms and other methods: github.com/perl6/roast/commit/d663...e76c64f2ba |
|||
| roast/6.c-errata: e20b1008ba | (Zoffix Znet)++ | S16-io/print.t Fix incorrect IO::Handle.print: @array 1) It expects different output for @array than for $array 2) This is due to the signature in IO::Handle.print being *@, while in IO::Handle.say (and with my patch in .put) and &say, &put, and &print it's **@ 3) Looking at the commit that brought the test, it appears the test was merely covering the current, at the time, behaviour, rather than a product of conscious design decision to make behaviour different from subroutine forms and other methods: github.com/perl6/roast/commit/d663...e76c64f2ba |
|||
| roast: 4d0f97a922 | (Zoffix Znet)++ | S16-io/put.t [io grant] Add &put/IO::Handle.put tests |
08:18 | ||
| rakudo/nom: 601cdb6d58 | (Zoffix Znet)++ | t/spectest.data Add S16-io/put.t to list of test files to run |
|||
| jnthn | morning o/ | 08:49 | |
| yoleaux | 00:53Z <MasterDuke> jnthn: if it helps, here's the MVM_dump_backtrace output at the problematic coerce_ni when running `say(100000000000000009)` gist.github.com/MasterDuke17/a34c6...a67f0249db | ||
| Zoffix | \o | 09:06 | |
| |Tux| | This is Rakudo version 2017.05-21-g601cdb6d5 built on MoarVM version 2017.05-9-g37460c7a | 09:45 | |
| csv-ip5xs 2.585 | |||
| test 12.491 | |||
| test-t 4.264 - 4.275 | |||
| csv-parser 12.967 | |||
| lizmat | Files=1192, Tests=58679, 206 wallclock secs (12.44 usr 4.81 sys + 1220.11 cusr 116.30 csys = 1353.66 CPU) | 09:48 | |
| yoleaux | 21 May 2017 21:36Z <Zoffix> lizmat: any idea if the Cool:D and Mu candidates can be merged together? I see the comment about optimization was deleted... do we still need to candidates with identical bodies? github.com/rakudo/rakudo/commit/b0...a4b7d7625e | ||
| Zoffix | buggable: speed 6 | 09:50 | |
| buggable | Zoffix, ▁▁▇▇▂▂ data for 2017-05-20–2017-05-22; range: 4.225s–4.607s; 1% slower | ||
| Zoffix | \o/ | ||
| lizmat | m: dd Pair.new(:a<b>) # now it is silent ? | 09:52 | |
| camelia | (Mu) => Mu | ||
| Zoffix | Unless the slowage is still there and got offset by .print/.put sig change | ||
| m: sub foo (*@) { }; for ^1000_00 { $ = foo "a", "b", "c" }; say now - INIT now | 09:53 | ||
| camelia | 0.3198904 | ||
| Zoffix | m: sub foo (**@) { }; for ^1000_00 { $ = foo "a", "b", "c" }; say now - INIT now | ||
| camelia | 0.28454634 | ||
| Zoffix | lizmat: oops. Will fix in a sec | ||
| lizmat | Zoffix: I have a fix | ||
| Zoffix | ok | ||
| Yeah, I only tested for wrong positionals :/ | 09:54 | ||
| lizmat | spectesting now | ||
| Zoffix | m: dd Pair.new: <a b c> | ||
| camelia | Cannot resolve caller new(Pair: List); none of these signatures match: (Pair $: Cool:D \key, Mu \value, *%_) (Pair $: Mu \key, Mu \value, *%_) (Pair $: Mu :$key, Mu :$value, *%_) in block <unit> at <tmp> line 1 |
||
| lizmat | m: dd Pair.new(:a<b>) # will give the same error | ||
| camelia | (Mu) => Mu | ||
| lizmat | m: my $a = $*VM; for ^100000 { Pair.new($a,42) }; say now - INIT now # not cool | 09:59 | |
| camelia | 0.13321350 | ||
| lizmat | m: my $a = "foo:; for ^100000 { Pair.new($a,42) }; say now - INIT now # cool | ||
| camelia | 5===SORRY!5=== Error while compiling <tmp> Unable to parse expression in double quotes; couldn't find final '"' at <tmp>:1 ------> 3new($a,42) }; say now - INIT now # cool7⏏5<EOL> expecting any of: horizontal whitespace… |
||
| lizmat | m: my $a = "foo:"; for ^100000 { Pair.new($a,42) }; say now - INIT now # cool | ||
| camelia | 0.0984492 | ||
| lizmat | feels to me the Cool candidate is still needed | ||
| m: say 0.13321350 / 0.0984492 | 10:00 | ||
| camelia | 1.3531192 | ||
| Zoffix | OK. Perhaps could use a comment there about it being there for optimization reasons | ||
| lizmat | yeah, just added | 10:01 | |
| Geth | rakudo/nom: 85bef661f0 | (Elizabeth Mattijsen)++ | src/core/Pair.pm Make sure that Pair.new(:foo<bar>) dies Also add comment on the need of the Cool:D candidate. |
||
| lizmat | actually, I think the above benchmark is flawed | 10:02 | |
| m: my $a = Str; for ^100000 { Pair.new($a,42) }; say now - INIT now # not Cool:D | 10:03 | ||
| camelia | 0.102694 | ||
| lizmat | m: my $a = "foo"; for ^100000 { Pair.new($a,42) }; say now - INIT now # Cool:D | ||
| camelia | 0.09789931 | ||
| lizmat | m: say 0.102694 / 0.09789931 | 10:04 | |
| camelia | 1.04897573 | ||
| lizmat | so, more like 5% faster | ||
| still for something that is done a lot with e.g. iterating over a hash.. seems worthwhile | |||
| Geth | roast: ea41dcd0d5 | (Zoffix Znet)++ | S02-types/pair.t Test wrong named args to Pair.new throw Rakudo fix: github.com/rakudo/rakudo/commit/85bef661f0 |
10:06 | |
| Zoffix | ehehe, we have exactly 0 tests for &prompt | 10:23 | |
| and it's documented :) | |||
| lizmat assumes they will get promptly added now ? | 10:24 | ||
| Zoffix | :) | ||
| This brings me to wanting to make $msg default to '' | |||
| as in: my $foo = prompt; just waits for a line of text on $*IN without showing any messages | |||
| 'cause &get uses $*ARGFILES, so you're either left with `my $foo = prompt '';` which is kinda ewww or `my $foo = $*IN.get` which is also ewwy | 10:25 | ||
| Geth | rakudo/nom: b43db636ab | (Elizabeth Mattijsen)++ | 2 files Make (Bag|Mix).AT-KEY about 10% faster By only needing to do a lookup in the underlying hash once on a match. Keeps the original Baggy.AT-KEY implementation for subclasses: not possible to do the (Bag|Mix) implementation in the role, as we cannot initialize a class lexical in a role :-( . At least not in the Setting. |
10:58 | |
| Zoffix | w00t! Another Perl 6 book: www.indiegogo.com/projects/book-we...bsite--2#/ | 11:05 | |
| wow 11 backers already | |||
| Can't say I was all that impressed with a few Gábo's articles that I've read... but it's good to have more books | 11:06 | ||
| ZofBot: should I spring the $50 to get preview copies? | 11:07 | ||
| ZofBot | Zoffix, ACCEPTS faster now Unhandled exception in code scheduled on thread 27 Unhandled exception in code scheduled on thread 30 too many open files :| ;( m: say 4 | ||
| Zoffix | I guess that means I should hurry the hell up with Tardigrade so that it might make the book ^_^ | 11:08 | |
| pmurias | what's Tardigrade? | 11:12 | |
| tadzik | ZofBot: Are your replies a markov chain of this channel? :o | 11:13 | |
| ZofBot | 57 "199:" » m |
||
| tadzik | I guess that answers my question | ||
| Zoffix | :> | ||
| tadzik: the original brain was a scrape of design.perl6.org | 11:14 | ||
| it now evolved a bit... | |||
| tadzik | hehe | ||
| ...or did it... | |||
| or are we all adhering to this design too :o | 11:15 | ||
| Zoffix | ugh indiegogo.com doesn't take PayPal :| | 11:16 | |
| lizmat | .seen masak | 11:30 | |
| yoleaux | I saw masak 19 May 2017 08:42Z in #perl6-dev: <masak> it creates a WhateverCode of the whole expression, I guess | ||
| Geth | rakudo/nom: 0646d3fa46 | (Zoffix Znet)++ | src/core/io_operators.pm [io grant] Allow no-arg &prompt It's not entirely unheard of to not want to include any text message to the user when prompting for some input. It's a bit antisocial to force the user to specify `''` arg for such cases. Worse, they might introduce a subtle bug into their code by switching to use `get` for a message-less `prompt`, but `get` defaults to `$*ARGFILES`, instead of `$*IN` |
11:31 | |
| roast: 125fe18489 | (Zoffix Znet)++ | S16-io/prompt.t [io grant] Add &prompt tests |
|||
| nqp: 23cea1133c | pmurias++ | src/vm/js/Operations.nqp [js] Fix bug with neverreposses being ignore when used in void context |
|||
| nqp: f2b5270337 | pmurias++ | 2 files [js] Implement nqp::loadbytecodefh |
|||
| rakudo/nom: bf1d0ada35 | (Zoffix Znet)++ | t/spectest.data Run S16-io/prompt.t tests as part of spectest |
11:32 | ||
| Zoffix | Why yes, atop, close all my instances when I accidentally press CTRL+Q instead of CTRL+W -_ | 11:37 | |
| *atom | |||
| ilmari | chrome gets this right, by making the quit shortcut ctrl-shift-q (and there's a firefox extension to do the same) | 11:39 | |
| Zoffix | Yeah, I have the firefox extension. | 11:41 | |
| Geth | nqp: cono++ created pull request #360: Add mapping of the op code get_port_sk |
11:49 | |
| rakudo: cono++ created pull request #1086: Update localport if we made bind on port 0 |
11:50 | ||
| cono | jnthn: here is PR for what we discussed yesterday: github.com/MoarVM/MoarVM/pull/600 at the bottom of it you can find links to the nqp and rakudo PR's. Three is no spec-test PR yet. | 11:54 | |
| lizmat | jnthn: a though re native attributes in Roles: perhaps they could be handled in the Optimizer ? | 12:11 | |
| *thought | |||
| *sigh* | 12:12 | ||
| Geth | rakudo/nom: ff04a37c4b | (Elizabeth Mattijsen)++ | 3 files Streamline (Set|Bag|Mix).new(), there can only be one! Set.new() did not return set(), but it did handle subclassing. Bag.new() returned bag(), but did not handle subclassing. Mix.new() returned mix(), but did not handle subclassing. |
12:15 | |
| roast: eb435234a2 | (Elizabeth Mattijsen)++ | 3 files Set|Bag|Mix.new returns the empty set|bag|mix |
12:21 | ||
| nine | Puh...openSSL braucht da kurzfristig scho 900 MB RAM | 12:30 | |
| moritz | nine: wrong channel or wrong language :-) | ||
| nine | moritz: argh...wrong channel indeed. As much as I love the discovery of irssi's split window mode, it does require extra care. | 12:36 | |
| lizmat | m: say Set (<=) Set # awh | 12:37 | |
| camelia | Invocant of method 'total' must be an object instance of type 'Setty', not a type object of type 'Set'. Did you forget a '.new'? in block <unit> at <tmp> line 1 |
||
| lizmat | fixing now | 12:38 | |
| Geth | rakudo/nom: accf519850 | (Elizabeth Mattijsen)++ | 3 files Get Baggy.AT-KEY optimization back into role We don't need no lexical, we can BEGIN :-) |
12:46 | |
| rakudo/nom: ad8fa55297 | (Elizabeth Mattijsen)++ | src/core/set_operators.pm Make sure that Setty:U is treated like any type object Fixing Set (<) Set and friends. |
|||
| rakudo/js: 0cb7e5f287 | pmurias++ | src/vm/js/perl6-runtime/runtime.js [js] Hide some debugging messages |
13:35 | ||
| rakudo/js: c176289ffe | pmurias++ | Configure.pl Report a problem when the --backends is incompatible with the --with-nqp |
|||
| rakudo/nom: 5c8e3f3ab9 | (Elizabeth Mattijsen)++ | src/core/set_operators.pm Define superset ops in terms of subset ops No need to implement the same functionality twice. Done in preparation for subset ops refactor. |
13:46 | ||
| nqp: f9f6667dc5 | (Jonathan Worthington)++ | src/vm/jvm/QAST/Compiler.nqp Correct decodertakeline op return type. |
13:54 | ||
| Zoffix ponders what IO::CatHandle should do for write methods... | 13:56 | ||
| like $fh.say: "meows" | |||
| Like in here I was thinking of mirroring it into all the given handles: github.com/rakudo/rakudo/commit/03...605b31d37a | 13:58 | ||
| But now I think that's both (a) not really useful; (b) doesn't scale, since it requires all handles to be open for writing, and you hit the open file limit | |||
| lizmat | isn't IO::CatHandle just a IO::Handle wrt to writing ?? | ||
| ah... sorry | 13:59 | ||
| lizmat shuts up again | |||
| well, no writing to IO::CatHandle | |||
| oops | |||
| :-) | |||
| Zoffix | Well, writing to the currently active handle is another option, but then it's like... why use a cathandle for this then. And third option is writing X bytes/chars/lines/words and automatically switching to another file, but that feels more of a narrow use case best left for module-space | 14:01 | |
| Zoffix will go with "die X::NIY" for write methods for now | |||
| lizmat | sounds like a plan to me :-) | ||
| Zoffix | .seen cygx | 14:18 | |
| yoleaux | I saw cygx 21 May 2017 16:40Z in #perl6: <cygx> not sure how this is supposed to work, but you could try locating you moarvm's Makefile and remove that part from CFLAGS and build manually | ||
| Zoffix | .ask cygx would you recommend .seek/.tell to throw if called on a handle that isn't in binary mode? I recall you saying they are technically binary operations when I had that case where .tell was giving wrong result after some text read operation | 14:19 | |
| yoleaux | Zoffix: I'll pass your message to cygx. | ||
| Geth | rakudo/nom: 32eb285f18 | (Elizabeth Mattijsen)++ | src/core/set_operators.pm Make (<=) and (>=) about 50x faster Based on a 25/26 elem Set. Doing a (<=) or (>=) on itself is now shortcut, as that is always True, for potentially infinite speed improvement (as the identity check is *very* cheap). |
14:52 | |
| rakudo/js: df77eb6a44 | pmurias++ | 3 files Add missing paren in message. |
14:53 | ||
| lizmat | afk for a bit& | 15:06 | |
| cono | jnthn: Huston we have a problem :D pastebin.com/CzhThVRa | 15:11 | |
| somewhere in thread.finish it dies | 15:12 | ||
| any tips where to set break point? | |||
| hm, in debugger it just works fine :( hate this thing. Walked from this: MVM_thread_join until the end | 15:20 | ||
| ah, looks like I was able to segfault it in debugger: pastebin.com/0khmkbT3 | 15:22 | ||
| jnthn | At a guess, you'll have assumed something is thread safe that ain't | 15:30 | |
| otoh | 15:31 | ||
| We know that sockets ain't on master :) | |||
| (the sync type, not the IO::Socket::Async type) | |||
| Which is what I'm doing in my branch | |||
| That kind of segv isn't the typical failure mode though | |||
| [Coke] | ... ok, it's weird to me that -dev is filling up backscroll (I hate this irc client!) but #perl6 isn't. | 15:37 | |
| mst | "filling up" ? | 15:38 | |
| [Coke] | too many sends, this client defaults to throwing away the oldest. | 15:40 | |
| so then I have to go back to the web logs to review. if the buffer doesn't fill, I can review in-client. | |||
| (irssi) | 15:41 | ||
| (and because of how it does it, I can't even see what the last line I read was.) | |||
| Zoffix | heh | 16:28 | |
| Well, that's good. There's no such thing as too much -dev :) | 16:29 | ||
| #perl6 looks quite filled up to me.... | |||
| Zoffix notices a spam comment on the IO grant: news.perlfoundation.org/2017/01/gra...ation.html | 18:52 | ||
| How dare they! | |||
| Man, there's no end to this grant... I don't think I'll ever be doing another one :| | 18:53 | ||
| [Coke] | (spam comment)... I'll delete it. | 18:54 | |
| Zoffix | \o/ | ||
| [Coke] | ... I can't, it's makoto's post. | 18:55 | |
| Zoffix | ah heh :) | ||
| Geth | rakudo/nom: 431ed4e30e | (Elizabeth Mattijsen)++ | src/core/set_operators.pm Make (<) and (>) about 40x faster Based on a 25/26 elem Set. Doing a (<) or (>) on itself is now shortcut, as that is always False, for potentially infinite speed improvement (as the identity check is *very* cheap). |
||
| Zoffix | Is there any downside to using method meth (::?CLASS:D:) {} instead of method meth (SomeClass:D:) {} ? | 19:08 | |
| like perf or anything... | 19:09 | ||
| dogbert17 | commit: 2016.06 my $l = (1, 2, 3); say (0, slip $l).perl; | 19:25 | |
| committable6 | dogbert17, ¦2016.06: «(0, $(1, 2, 3))» | ||
| dogbert17 | m: my $l = (1, 2, 3); say (0, slip $l).perl; | 19:26 | |
| camelia | (0, 1, 2, 3) | ||
| dogbert17 | commit: 2016.08 my $l = (1, 2, 3); say (0, slip $l).perl; | ||
| committable6 | dogbert17, ¦2016.08: «(0, $(1, 2, 3))» | ||
| dogbert17 | commit: 2016.10 my $l = (1, 2, 3); say (0, slip $l).perl; | ||
| committable6 | dogbert17, ¦2016.10: «(0, $(1, 2, 3))» | ||
| dogbert17 | commit: 2016.11 my $l = (1, 2, 3); say (0, slip $l).perl; | ||
| committable6 | dogbert17, ¦2016.11: «(0, 1, 2, 3)» | ||
| dogbert17 | is the new behavior ^^ correct? | 19:27 | |
| Zoffix | yup | 19:29 | |
| dogbert17 | Zoffix: thx, time to update some docs then :) | 19:30 | |
| Zoffix | dogbert17: well, looks correct to me, though seems it got that way by accident | ||
| c: 37d0e4661414de827de35 my $l = (1, 2, 3); say (0, slip $l).perl; | 19:31 | ||
| committable6 | Zoffix, ¦37d0e46: «(0, 1, 2, 3)» | ||
| Zoffix | c: 37d0e4661414de827de35~1 my $l = (1, 2, 3); say (0, slip $l).perl; | ||
| committable6 | Zoffix, ¦37d0e4661414de827de35~1: «(0, $(1, 2, 3))» | ||
| Zoffix | And that commit is a perf improvemnt: github.com/rakudo/rakudo/commit/37...a81d1d23df | ||
| hm | |||
| Zoffix wishes TimToady was around right now :) | |||
| He knows this stuff well | |||
| dogbert17: now, I'm starting to feel it's wrong lol :) | 19:32 | ||
| if it were (0, |$l) then yeah, it'd be right, but I think (0, slip $l) is a different thing | |||
| dogbert17 | I haven't made the update just yet :) | ||
| Zoffix | or something | ||
| I don't know this stuff | |||
| Zoffix finally admits and shuts up :D | 19:33 | ||
| m: my $l = (1, 2, 3); say (0, $(slip $l)).perl; | |||
| camelia | (0, 1, 2, 3) | ||
| Zoffix | well, this is definitely wrong :) | ||
| dogbert17 | one bug at least then :) | 19:34 | |
| and lizmat is writing the weekly atm I think | 19:35 | ||
| commit: 2016.10 m: my $l = (1, 2, 3); say (0, $(slip $l)).perl; | |||
| committable6 | dogbert17, ¦2016.10: «(0, $(1, 2, 3))» | ||
| Zoffix | She doesn't have to fix it. Just file it ¯\_(ツ)_/¯ | 19:36 | |
| dogbert17 | will do | 19:37 | |
| Zoffix | m: multi foo (@a) { say "here"; dd @a }; multi foo (+a) { say "there"; dd a }; my $l = (1, 2, 3); foo $l | ||
| camelia | here (1, 2, 3) |
||
| Zoffix | m: multi foo (+a) { say "there"; dd a }; my $l = (1, 2, 3); foo $l | ||
| camelia | there ($(1, 2, 3),) |
||
| dogbert17 wonders how this bug managed to slip through our tests :) | 19:38 | ||
| Zoffix | m: my $l = (1, 2, 3); say (0, $(item $(slip $l))).perl; | 19:39 | |
| camelia | (0, 1, 2, 3) | ||
| Zoffix doesn't get how that one manages to slip all the way through the item stuff :| | |||
| /win 8 | 19:40 | ||
| buggable | Zoffix, Thank you for entering Accidental /win Lottery! The next draw will happen in 2 weeks, 3 days, 4 hours, 19 minutes, and 18 seconds | ||
| Zoffix | huh | ||
| lizmat | /win 6 | 19:42 | |
| buggable | lizmat, Thank you for entering Accidental /win Lottery! The next draw will happen in 2 weeks, 3 days, 4 hours, 17 minutes, and 42 seconds | ||
| dogbert17 | lizmat: backlog a screenful plz | ||
| lizmat | dogbert17: yeah, please RT it | ||
| dogbert17 | will do | 19:43 | |
| lizmat | dogbert17: fwiw, I found several bugs today in set operators that have gone undetected for years :-( | ||
| dogbert17 | oops | ||
| [Coke] | lizmat: but also, unreported. | 19:44 | |
| lizmat | m: Date (<=) Date # now works | ||
| camelia | WARNINGS for <tmp>: Useless use of "(<=)" in expression "Date (<=) Date" in sink context (line 1) |
||
| lizmat | m: say Date (<=) Date # now works | ||
| camelia | True | ||
| [Coke] | better that you found them than a user. | ||
| lizmat | m: say Set (<=) Set # now also works | ||
| camelia | True | ||
| dogbert17 | commit: 2016:10 say <a b> X~ |(1, 2, 3) # | ||
| committable6 | dogbert17, ¦2016:10: «Cannot find this revision (did you mean “2016.10”?)» | ||
| dogbert17 | commit: 2016.10 say <a b> X~ |(1, 2, 3) # | 19:45 | |
| committable6 | dogbert17, ¦2016.10: «(a123 b123)» | ||
| awwaiid | lizmat: is that one of those twisty things of a set that contains itself so we can break mathematics? | ||
| lizmat | awwaiid: it all boils down that the Set type object is not a set, it needs to be coerced to a set first :-) | 19:48 | |
| m: dd Set.Set | 19:49 | ||
| camelia | set(Set) | ||
| geekosaur | that sounds wrong | 19:50 | |
| awwaiid | but oh so right | ||
| geekosaur | I mean, I read that as a Set containing a Set type object. but I'm not sure what a Set type object should be, aside from a special case or not-a-set | 19:51 | |
| lizmat | m: dd Int.Set # does this make sense, geekosaur? | 19:52 | |
| camelia | set(Int) | ||
| geekosaur | (and yes, this does fall down the Russell rabbit hole) | ||
| dogbert17 | lizmat: RT #131344 | ||
| synopsebot6 | Link: rt.perl.org/rt3/Public/Bug/Display...?id=131344 | ||
| lizmat | dogbert17: noted | ||
| geekosaur | same thing, a Set containing a type object. which arguably is not the same as a type object _and_ not the same as whatever a Set type object would mean when used as a Set | ||
| dogbert17 was sorely tempted to write '[REGRESSION] behavior of slip has slipped' | 19:53 | ||
| Zoffix | $ rakudobrew switch moar-2107.04.3 | ||
| lizmat | geekosaur: well, anything that's not a set is coerced to a set first before being compared with e.g. (<=) | ||
| geekosaur | I mean, I could see a Set type object being autocoerced to an empty set in some circumstances... but *not* all. on the other hand, that is more or less what we expect numbers and strings to do, so. | ||
| Zoffix | Sorry, I have no idea what 'moar-2107.04.3' is | ||
| k'comn, rakudobrew! 100 year language and what not! | 19:54 | ||
| geekosaur | all roads here are wrong, some subtly and some severely | ||
| lizmat | the Set type object is *not* the empty set | ||
| one could argue that the Set type object is an implementation detail | |||
| Zoffix | Imagine it called FooBar. You get same behaviour FooBar.Set => set(FooBar) | 19:55 | |
| geekosaur | I guess that means I didn';t just say that? so I guess I'll just back out | ||
| lizmat | geekosaur: dealing with sets is difficult enough with one set of eyes: we can use all the eyes we can get! | 19:58 | |
| Zoffix | ugexe: FWIW, I see zef here failing with "no method .as on Seq": ci.appveyor.com/project/ufobat/Bai...nch/master | 20:00 | |
| ugexe: I see some method .as in zef's sauce; looks like there's some path that leads to a Seq rather than whatever has .as object | |||
| ugexe | thats also moar-2016.03 | 20:01 | |
| Zoffix | oh lol | 20:02 | |
| Geth | roast: cono++ created pull request #270: Rework IO-Socket-INET test to make it more self-sufficient |
20:16 | |
| cono | So ran a test one at a time, looks fine, but when I run all of them it segfaults after the third one :( Somewhere in thread.finish. I'll look into it but no guarantee that I can get it to work, so rely on you about thread stuff :) | 20:19 | |
| pmurias | awwaiid: the build instructions for rakudo.js will be "perl Configure --backends=js --gen-nqp", I just have to set up a few things for that to work | 20:20 | |
| AlexDaniel | /win 0 | 20:35 | |
| buggable | AlexDaniel, Thank you for entering Accidental /win Lottery! The next draw will happen in 2 weeks, 3 days, 3 hours, 24 minutes, and 2 seconds | ||
| AlexDaniel | and 2 seconds! | 20:36 | |
| oh that precision! | |||
| buggable: but how many milliseconds? | 20:39 | ||
| Zoffix | It's a secret :) | 20:41 | |
| buggable: lottery | |||
| buggable: source | 20:42 | ||
| buggable | Zoffix, See: github.com/zoffixznet/perl6-buggable | ||
| Zoffix | buggable: draw | ||
| buggable | Zoffix, The next Accidental /win Lottery draw will happen in 2 weeks, 3 days, 3 hours, 17 minutes, and 35 seconds. Currently have 13 ballots submitted by 10 users! | ||
| Zoffix | hehe | ||
| AlexDaniel | /win 42 | 20:44 | |
| buggable | AlexDaniel, Thank you for entering Accidental /win Lottery! The next draw will happen in 2 weeks, 3 days, 3 hours, 15 minutes, and 15 seconds | ||
| AlexDaniel | buggable: draw | ||
| buggable | AlexDaniel, The next Accidental /win Lottery draw will happen in 2 weeks, 3 days, 3 hours, 15 minutes, and 9 seconds. Currently have 14 ballots submitted by 10 users! | ||
| Geth | rakudo/newer-cat-handle: c86e8c9098 | (Zoffix Znet)++ | 2 files Sketch of IO::CatHandle Not workable yet, but stashing it so I could work on it from other boxes. |
20:47 | |
| roast/newer-cat-handle: d638e18587 | (Zoffix Znet)++ | S32-io/io-cathandle.t Start sketching CatHandle tests |
20:48 | ||
| Zoffix is done hacking for the day | |||
| AlexDaniel | c: 2014.05~4 say 42 | 21:37 | |
| committable6 | AlexDaniel, ¦2014.05~4: «42» | ||
| AlexDaniel | there's still a hole between 2014.05 and 2015.02 I think, so stuff isn't bisectable yet… but it's getting close :) | 21:39 | |
| Zoffix | :) | 21:40 | |
| AlexDaniel | actually, I'm not sure | 21:42 | |
| bisect: old=2014.01 say ‘hello’ | |||
| bisectable6 | AlexDaniel, Bisecting by exit code (old=2014.01 new=431ed4e). Old exit code: 1 | ||
| AlexDaniel, bisect log: gist.github.com/7b30ac12b4461ce7bd...ad0bdb5899 | |||
| AlexDaniel, (2015-02-23) github.com/rakudo/rakudo/commit/a2...6dd4d50300 | |||
| AlexDaniel | bisect: old=2014.01 say ∞ | ||
| bisectable6 | AlexDaniel, Bisecting by exit code (old=2014.01 new=431ed4e). Old exit code: 1 | ||
| AlexDaniel, bisect log: gist.github.com/ff3d1a30beb2a05331...c39a26b007 | |||
| AlexDaniel, (2015-12-18) github.com/rakudo/rakudo/commit/1f...48b362ab07 | |||
| AlexDaniel | to be honest I have no idea how much is done | 21:43 | |
| it's just not done yet… | |||
| Zoffix | heh... "because it's Friday and I'm feeling expansive" I didn't realize we got ∞ kinda on a whim :D | 21:57 | |
| Zoffix likes ∞ a lot | |||
| Geth | rakudo/nom: 379ef6f1d4 | (Zoffix Znet)++ | src/core/IO/Handle.pm Move $close handling in IO::Handle.comb/split To .slurp (Also add a TODO comment for when we get Cat) |
22:02 | |
| AlexDaniel | bisect: say −42 | 22:06 | |
| bisectable6 | AlexDaniel, On both starting points (old=2015.12 new=431ed4e) the exit code is 0 and the output is identical as well | ||
| AlexDaniel, Output on both points: «-42» | |||
| AlexDaniel | bisect: old=2014.01 say −42 | ||
| bisectable6 | AlexDaniel, Bisecting by exit code (old=2014.01 new=431ed4e). Old exit code: 1 | ||
| AlexDaniel, bisect log: gist.github.com/4df2a2749d9ab4db1b...1f99891760 | |||
| AlexDaniel, There are 2 candidates for the first “new” revision. See the log for more details | |||
| AlexDaniel | github.com/rakudo/rakudo/commit/33...f29ee099a4 | ||
| oh, but that's very recent | |||
| Zoffix | 1-day less recent than infinity :) | 22:10 | |
| And it's quite the opositite, I hate − and I want it removed :D | |||
| AlexDaniel | bisect: old=2014.01 say π | 22:23 | |
| bisectable6 | AlexDaniel, Bisecting by exit code (old=2014.01 new=431ed4e). Old exit code: 1 | ||
| AlexDaniel, bisect log: gist.github.com/34c6d5880c782814f6...c86aaba5e0 | 22:26 | ||
| AlexDaniel, There are 407 candidates for the first “new” revision. See the log for more details | |||
| AlexDaniel | told ya, not done yet :) | ||
| nebuchadnezzar | Hello | 22:28 | |
| AlexDaniel | o/ | ||
| Zoffix | \o | 22:29 | |
| nebuchadnezzar | I'm trying to update the Debian packages and I wonder if its normal that --libdir is not passed to gcc: paste.debian.net/934241/, because the moar binary ends with “libmoar.so => not found” paste.debian.net/934242/, any hints? | 22:31 | |
| lizmat | And another Perl 6 Weekly hits the Net: p6weekly.wordpress.com/2017/05/22/...-21-yap6b/ | 22:32 | |
| that took a little longer than I expected | 22:33 | ||
| lizmat decides to call it a day | |||
| good night, #perl6-dev! | |||
| Zoffix | night | 22:35 | |
| nebuchadnezzar: IIRC moar recentlyish had some changes done to its build chain. Maybe worth mentioning in #moarvm to see if some eyes (timotimo) spot it | 22:41 | ||
| nebuchadnezzar | I think I found, I'll report there | 22:42 | |
| timotimo | uh oh | 22:50 | |
| i've done a boo boo again? |