Perl 6 - the future is here, just unevenly distributed

IRC log for #perl6-dev, 2016-10-08

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

All times shown according to UTC.

Time Nick Message
00:50 MasterDuke joined #perl6-dev
01:48 ilbot3 joined #perl6-dev
01:48 Topic for #perl6-dev is now Perl 6 language and compiler development 2.0 | Logs at http://irclog.perlgeek.de/perl6-dev/today
05:27 dalek roast: d8650f2 | usev6++ | S32-num/int.t:
05:27 dalek roast: Test for X::Numeric::Overflow passes on JVM
05:27 dalek roast: review: https://github.com/perl6/roast/commit/d8650f283f
05:27 dalek roast: 0981b4b | usev6++ | S05-mass/charsets.t:
05:27 dalek roast: Unfudge tests that require Java 8 (unicode 6.1)
05:27 dalek roast:
05:27 dalek roast: The tests in question require unicode 6.1 and therefore
05:27 dalek roast: fail with Java < 8. On the other hand we already have
05:27 dalek roast: unfudged tests that require Java 8 elsewhere.
05:27 dalek roast:
05:27 dalek roast: Java 8 was released 2014-03-18 so it seems reasonable
05:27 dalek roast: to unfudge those tests.
07:02 FROGGS joined #perl6-dev
07:31 RabidGravy joined #perl6-dev
07:36 [Tux] This is Rakudo version 2016.09-144-g2285d35 built on MoarVM version 2016.09-27-g0bdbd6e
07:36 [Tux] csv-ip5xs        3.169
07:36 [Tux] test            16.171
07:36 [Tux] test-t           7.026
07:36 [Tux] csv-parser      17.886
08:45 psch hm, i'm not too happy about unfudging tests needing java 1.8
08:46 psch mostly 'cause hack is only 1.7.0_111 :l
08:46 psch s/only/on/
08:47 psch although that seems to be a distro version thing.  1.8 isn't in apt-cache
08:50 bartolin psch: I have no strong opinion about that. but I would prefer to keep it consistent. so, if we revert the above commit we should also fudge some other tests which don't pass with jdk 1.7
08:50 nine I guess hack could also be updated
08:50 bartolin (or do I remember that wrong? I'm mostly testing with jdk 1.8 now)
08:50 psch bartolin: well, i'd prefer we make 1.8 a hard-ish requirement on the spectest-side
08:51 psch as in, let people build with 1.7 if they want to, and only force 1.7 on the compiler as well
08:51 bartolin even better
08:51 psch but failing tests due to 1.7 are eh
08:51 psch although we probably should note in roast that those *are* 1.7 failures
08:51 psch maybe even skip if we can fudge that somehow...
08:51 psch nine: yes please :)
08:54 psch j: $*VM.properties<java.version>.say
08:54 camelia rakudo-jvm 2a1605: OUTPUT«1.7.0_79␤»
08:54 psch camelia is also some 30 minor patches behind hack
08:54 nine psch: I don't even have an account on hack ;) But you could have one on my server.
08:54 * nine goes off to update camelia
08:54 nine Should I install jdk 1.8 on camelia instead?
08:54 psch nine: thanks, i'll just bugged moritz about hack though :)
08:55 psch yeah, if only for unicode
08:55 psch i'm not sure we have anything else that depends on 1.8, but it might be somewhat faster too i hope :)
08:58 bartolin I'm afraid we have some kind of a structural problem with regard to the unicode version on JVM anyway. with moarvm we know which unicode version we support -- with jvm that depends on the locally installed java version
08:58 bartolin so, I think it would be nice to have a way to fudge according to the java version (or the supported unicode version)
08:59 * bartolin doesn't know about a simple way to do that
09:00 bartolin errands &
09:00 psch well, whatever the harness does to test for jvm or moar could probably be extended to $*VM.properties<java.version> if $backend eq 'jvm' or something
09:01 psch although i'm not sure about the fudge syntax, that'd have to be something relative which means more parsing for the fudger
09:01 psch s/harness/fudger/
09:02 psch hm, although we could probably go with a min version
09:03 psch hm, the java 9 RC is planned for 2017-01-26
09:06 psch ohh, the process control changes look pretty neat
09:07 psch not sure we want to build Proc::Async on that, but it'd probably be easier than on 1.7 heh
09:08 psch but yeah, probably a bad idea, considering release is supposed to be on 2017-03-23 and there'll probably be a few months for distros etc to fully catch up and all...
09:08 camelia joined #perl6-dev
09:09 nine j: $*VM.properties<java.version>.say
09:09 camelia rakudo-jvm 2a1605: OUTPUT«1.8.0_101␤»
09:09 psch nine++
09:10 nine Oh, it didn't even have to rebuild?
09:10 psch well, the build targets 1.7
09:10 psch rakudo build that is
09:20 psch r: say gather do for ^4 { next if $_ < 2; .take }
09:20 camelia rakudo-moar 2285d3, rakudo-jvm 2a1605: OUTPUT«(2 3)␤»
09:20 psch r: say gather do for ^4 { redo if $_ < 2 && $++ == 0; .take }
09:20 camelia rakudo-moar 2285d3, rakudo-jvm 2a1605: OUTPUT«(0 1 2 3)␤»
09:20 psch r: say gather do for ^4 { .take; redo if $_ < 2 && $++ == 0;  }
09:20 camelia rakudo-jvm 2a1605: OUTPUT«Error in socket connection:org.perl6.nqp.runtime.UnwindException␤     at org.perl6.nqp.runtime.ThreadContext.<init>(ThreadContext.java:125)␤  at org.perl6.nqp.runtime.GlobalContext.getCurrentThreadContext(GlobalContext.java:340)␤ at org.perl6.nqp.runtime.G…»
09:20 camelia ..rakudo-moar 2285d3: OUTPUT«(0 0 1 2 3)␤»
09:20 psch r: say gather do for ^4 { .take; redo if $_ < 2 && $++ == 0; 1 }
09:20 camelia rakudo-moar 2285d3: OUTPUT«WARNINGS for <tmp>:␤Useless use of constant integer 1 in sink context (line 1)␤(0 0 1 2 3)␤»
09:20 camelia ..rakudo-jvm 2a1605: OUTPUT«WARNINGS for <tmp>:␤Useless use of constant integer 1 in sink context (line 1)␤Error in socket connection:org.perl6.nqp.runtime.UnwindException␤      at org.perl6.nqp.runtime.ThreadContext.<init>(ThreadContext.java:125)␤  at org.perl6.nqp.runtime.GlobalCo…»
09:20 psch humm
09:21 psch that's kinda extra weird
09:21 psch 'cause CX::Next and CX::Redo handlers are somewhat linked during codegen
09:21 psch as in, we handle codegen for them together
09:22 psch but CX::Last gets its own code path for handler generation
09:22 psch so the fact that redo and last don't work but next does..?
09:45 psch oh geez
09:45 psch shoulda probably checked that earlier...
09:45 psch ah nvm bad test case
09:56 psch r: 'my \x := gather do for ^3 { .take; last }; use nqp; say nqp::getattr(List.from-iterator(x.iterator), List, q[$!todo]).reify-until-lazy
09:56 camelia rakudo-moar 2285d3: OUTPUT«===SORRY!=== Error while compiling <tmp>␤Unable to parse expression in single quotes; couldn't find final "'" ␤at <tmp>:1␤------> ator), List, q[$!todo]).reify-until-lazy⏏<EOL>␤    expecting any of:␤        single quotes␤        …»
09:56 camelia ..rakudo-jvm 2a1605: OUTPUT«===SORRY!=== Error while compiling <tmp>␤Unable to parse expression in single quotes; couldn't find final "'" ␤at <tmp>:1␤------> ator), List, q[$!todo]).reify-until-lazy⏏<EOL>␤    expecting any of:␤        single quotes␤        t…»
09:56 psch r: my \x := gather do for ^3 { .take; last }; use nqp; say nqp::getattr(List.from-iterator(x.iterator), List, q[$!todo]).reify-until-lazy
09:56 camelia rakudo-moar 2285d3: OUTPUT«1␤»
09:56 camelia ..rakudo-jvm 2a1605: OUTPUT«Error in socket connection:org.perl6.nqp.runtime.UnwindException␤     at org.perl6.nqp.runtime.ThreadContext.<init>(ThreadContext.java:125)␤  at org.perl6.nqp.runtime.GlobalContext.getCurrentThreadContext(GlobalContext.java:340)␤ at org.perl6.nqp.runtime.G…»
09:56 psch that seems to be the most gutsy way to get that error afaict
09:57 psch as in, the UnwindException probably comes from reify-until-lazy on a List::Reifier that was build with gather/take *and* last..?
09:57 psch r: my \x := gather do for ^3 { .take; last }; use nqp; say nqp::getattr(List.from-iterator(x.iterator), List, q[$!todo]).reify-at-least(2)
09:57 ggoebel joined #perl6-dev
09:57 camelia rakudo-moar 2285d3, rakudo-jvm 2a1605: OUTPUT«1␤»
09:57 lizmat Files=1146, Tests=53274, 235 wallclock secs (13.55 usr  4.08 sys + 1408.17 cusr 137.00 csys = 1562.80 CPU)
10:07 TimToady joined #perl6-dev
10:17 bartolin just another thought wrt fudging and unicode support: *if* we are going to do that, wouldn't it be useful to have some optional condition like 'unicode >= 6.1' for the fudge syntax? that way roast wouldn't be polluted with checks for specific backend versions -- that infomation could be kept in the fudger
10:18 psch i suppose it depends on whether we to fudge specifically for unicode or for backend versions
10:18 psch i'm somewhat sure jvm doesn't bump unicode during minor patches, but not completely
10:25 FROGGS we could let the backends expose their supported unicode version
10:26 TimToady joined #perl6-dev
10:37 jnthn fwiw, I suspect to do NFG and other Perl 6 Unicode features right we may well end up shipping our own Unicode database on the JVM anyway
10:37 jnthn Which'd give us control over it
10:40 psch oh, right, that's a thing
10:45 FROGGS yes, that's the only sane way to go
10:46 FROGGS also, IIRC we are meant to let the user lexically choose the unicode version
10:46 FROGGS that too means we have do ship it ourselfs
10:47 * jnthn is happy to kick that particular can a little way down the road :)
10:48 jnthn Unicode's only stability policy is relatively strong, so I'm curious if such a thing would be overkill
10:48 timotimo own*
10:48 timotimo ownly? :)
10:48 jnthn uh, yes :)
10:49 jnthn Maybe I shoulda done coffee instead of tea this morning :)
12:29 ShimmerFairy jnthn: for what it's worth, I believe I wrote in the "set Unicode version" stuff into the spec more for telling old perl6's if your expectation of Unicode is too new for them. And even if that wasn't my intent at the time, such a feature is probably most useful for that :)
12:30 ShimmerFairy (e.g. a newly-added script with properties that don't match what they defaulted to in previous Unicode versions)
12:34 ShimmerFairy an even better example would be brand new properties, which are kinda hard to work around with an old Unicode version :P
12:38 nine Isn't that just something for the Perl 6 version?
12:39 ShimmerFairy nine: not unless we want to tie specific Unicode versions to Perl 6 versions, which we don't currently do. (That is, MoarVM's UCD is updated as new versions come out IIRC)
12:39 lucasb joined #perl6-dev
12:44 ShimmerFairy (not that a minimum Unicode version would be bad, I'm just not sure about "and no newer")
14:14 AlexDaniel joined #perl6-dev
14:51 jnthn Maybe given the Unicode stability policy, something like "`use 6.c` promises a minimum of Unicode 8, `use 6.d` promises a minimum of Unicode 9" etc.
14:52 jnthn Would be sufficient.
16:29 synopsebot6 joined #perl6-dev
17:51 bisectable6 joined #perl6-dev
17:55 bisectable6 joined #perl6-dev
17:58 bisectable6 joined #perl6-dev
18:11 dogbert17 o/
18:12 dogbert17 FWiW, sometimes the test t/spec/S17-supply/start.t, i.e throwing a lot of 'Invalid read of size 4', must run it many times to get that effect
18:13 dogbert17 it looks quite suspicious
18:14 dogbert17 looks like this
18:14 dogbert17 ==4344== Invalid read of size 4
18:14 dogbert17 ==4344==    at 0x416EA53: MVM_sc_get_object (sc.c:178)
18:14 dogbert17 ==4344==    by 0x416EBD1: MVM_sc_get_sc_object (sc.c:199)
18:14 dogbert17 ==4344==    by 0x40D5B3F: MVM_interp_run (interp.c:3013)
18:14 dogbert17 ==4344==    by 0x40F8B0F: start_thread (threads.c:77)
18:14 dogbert17 ==4344==    by 0x41E4756: uv__thread_start (in /home/dogbert/repos/rakudo/install/lib/libmoar.so)
18:14 dogbert17 ==4344==    by 0x45EAF71: start_thread (pthread_create.c:312)
18:14 dogbert17 ==4344==    by 0x44DAF8D: clone (clone.S:129)Y
18:18 dogbert17 ==4643==  Address 0x5aff1f0 is 24 bytes inside a block of size 108 free'd
18:18 dogbert17 ==4643==    at 0x402B3D8: free (in /usr/lib/valgrind/vgpreload_memcheck-x86-linux.so)
18:18 dogbert17 ==4643==    by 0x414E8DD: MVM_free (alloc.h:29)
18:18 dogbert17 ==4643==    by 0x414F806: gc_free (SCRef.c:114)
18:18 dogbert17 ==4643==    by 0x411A11F: MVM_gc_collect_free_nursery_uncopied (collect.c:580)
18:18 dogbert17 ==4643==    by 0x411520E: MVM_gc_global_destruction (orchestrate.c:511)
18:18 dogbert17 ==4643==    by 0x41C8CCF: MVM_vm_destroy_instance (moar.c:391)
18:18 dogbert17 ==4643==    by 0x8048EB8: main (main.c:194)
18:19 bisectable6 joined #perl6-dev
18:22 pmurias joined #perl6-dev
18:28 dalek nqp: d06cbaf | (Pawel Murias)++ | t/nqp/019-file-ops.t:
18:28 dalek nqp: Fix bug cause by refactoring.
18:28 dalek nqp: review: https://github.com/perl6/nqp/commit/d06cbaf1b4
18:28 dalek nqp: 4c697e3 | (Pawel Murias)++ | src/vm/js/ (3 files):
18:28 dalek nqp: [js] Get and set attributes using accessors.
18:28 dalek joined #perl6-dev
18:46 raiph joined #perl6-dev
18:53 dogbert17 my ramblings above have now been transformed to https://rt.perl.org/Public/Bug/Display.html?id=129832
18:58 dalek rakudo/nom: 8f14219 | MasterDuke17++ | src/Perl6/Metamodel/CurriedRoleHOW.nqp:
18:58 dalek rakudo/nom: Add shortname() method to CurriedRoleHOW
18:58 dalek rakudo/nom:
18:58 dalek rakudo/nom: Fixes RT #129830
18:58 dalek rakudo/nom: review: https://github.com/rakudo/rakudo/commit/8f1421951b
18:58 synopsebot6 Link:  https://rt.perl.org/rt3//Public/Bug/Display.html?id=129830
18:58 dalek rakudo/nom: 3ca0f8b | lizmat++ | src/Perl6/Metamodel/CurriedRoleHOW.nqp:
18:58 dalek rakudo/nom: Merge pull request #899 from MasterDuke17/RT129830
18:58 dalek rakudo/nom:
18:58 dalek rakudo/nom: Add shortname() method to CurriedRoleHOW
18:58 dalek rakudo/nom: review: https://github.com/rakudo/rakudo/commit/3ca0f8bc87
19:16 raiph .tell lizmat Please read https://www.reddit.com/r/perl/comments/557m4k/any_new_perl_6_books/d8ha7sd for a summary regarding Chas Owens' fears/assertions re NYI Uni and Str roundtripping. Perhaps everyone has already heard enough about it already but if not, maybe it's worth mentioning this sub-thread as a topic completely distinct from books in the
19:16 raiph weekly. Also, do you think an RT and/or doc patch are warranted?
19:51 dalek rakudo/more_sizeof_tests: 7c11722 | FROGGS++ | t/04-nativecall/12-sizeof. (2 files):
19:51 dalek rakudo/more_sizeof_tests: add more tests for nativesizeof()
19:51 dalek rakudo/more_sizeof_tests: review: https://github.com/rakudo/rakudo/commit/7c11722305
19:56 psch raiph++
19:56 psch that interaction seems to have been handled very gracefully
19:56 psch i'm not deep enough into Unicode to offer technical feedback though
20:05 arnsholt It's not at all clear to me *why* this is a problem
20:05 jnthn Str roundtrips *Unicode* just fine in so far as if you ask any other Unicode-aware program if the input and output are equivalent, they should answer yes (reference: http://unicode.org/faq/normalization.html#1 )
20:05 arnsholt Except possibly in the case where you're forced to interact with other programs that don't handle Unicode correctly
20:06 arnsholt Yeah, that's the thing. Str is Unicode; if you're relying on exact code point sequences you're a) doing it wrong, and b) not actually Unicode-compliant
20:07 jnthn What's being asked for is a way to roundtrip the exact codepoints that were read in, while at the same time actually wanting to work with them as codepoints rather than bytes. Compared to working with Unicode and working with bunches of bytes, that's a rather more niche use-case.
20:08 jnthn (Thus why it's not been prioritized.)
20:08 jnthn And yes, I think you'd generally want to do it when dealing with other things with "interesting" Unicode handling.
20:09 psch jnthn: iiuc we're doing what Unicode demands, but the poster demands backwards compat with not-quite Unicode compliant programs, without wanting to fall back to byte-like handling?
20:10 jnthn psch: Something like that
20:10 jnthn It's not an unreasonable request, but it would be an unreasonable default.
20:11 psch right, so it does exactly fall into the propose/speculated 'use Uni' space
20:11 jnthn Well, the Uni data type
20:11 jnthn Which will get more attention with time
20:11 psch oh, i'm not trying to push for it, don't get me wrong.  i just wanna understand the concerns raised in the post
20:12 psch well, and maybe also the "what we're gonna do about it"
20:12 psch ...considering that jvm is so far behind on NFG i might have to learn this stuff eventually anyway :)
20:12 psch (although maybe bartolin++ picks it up instead, they've been doing a hell of a job on things i couldn't figure out :) )
20:13 jnthn :-)
20:13 * jnthn is happy to see folks hacking on the JVM bits
20:14 psch i *still* have a big "are there giant performance snags nobody noticed" thought running around in my brain
20:14 psch but i'm fairly sure i don't know the architecture well enough to judge that in the first place
20:14 psch nevermind the jvm itself, sooo
20:15 psch anyway, yeah, the problem in the reddit post is sort of "my app is bad at unicode, and rakudo isn't. fix that in rakudo please"
20:15 psch if i understood this correctly at least
20:16 psch ...unfortunately i think we cannot reach a consensus there, basically at all
20:16 psch because "well if you use this pragma" it already makes it seem like you need "this pragma"
20:16 psch and using the pragma when you don't need it doesn't hurt either, because apps that do unicode right still deal with it correctly
20:17 psch feels somewhat faustian
20:17 jnthn I'd not say "doesn't hurt"
20:17 psch ...no, that's the wrong word.  "faustian" that is
20:17 jnthn "Turns O(1) things into O(n) things" hurts.
20:17 jnthn Which will be a side-effect
20:17 jnthn .chars on a Uni is O(n), not O(1) like on Str
20:18 psch oh, okay.  so that's the big gain when you know you're dealing with Unicode compliant apps
20:18 timotimo so we're not going to be creating synthetics for "ä in NFG", "ä in NFC", "ä in NKFC", ... ?
20:18 jnthn No
20:19 timotimo hm
20:19 jnthn We'll just keep an array of codepoints.
20:19 jnthn Uni is actually a VMArray today REPR-wise
20:19 timotimo and we'll offer stringy operations on top of that, yeah?
20:19 timotimo right
20:19 jnthn Yeah, though some are kinda hard-ish to define
20:19 timotimo so it's theoretically mutable ... do we allow it to be mutated?
20:19 jnthn No
20:19 timotimo OK, so string-y in that way, too
20:20 jnthn In fact we could base it on MultiDimArray to take advantage of fixed-width
20:20 timotimo ah
20:20 timotimo not that that's an advantage at the moment :P
20:20 jnthn Not yet, though will be in the future
20:20 timotimo performance-wise, i mean
20:20 timotimo right
20:21 psch .tell raiph check https://irclog.perlgeek.de/perl6-dev/2016-10-08#i_13363563 for more input re: that reddit post
20:21 psch oh wait
20:21 psch we still don't have that kinda bot here
20:21 psch geez
20:22 psch anyway, thanks for the explanation jnthn++ :)
20:22 * psch gets themselves bedwards
20:23 jnthn :)
20:23 jnthn Rest well
20:23 timotimo good bed, psch
20:24 timotimo jnthn: any clue about if we should make positional sizes unsigned across the board?
20:24 timotimo hm, maybe those repr ops predate us having real unsigned integers in our bytecode?
20:24 jnthn timotimo: I considered going down that path and didn't
20:25 jnthn It seems nice until you consider that pretty much all index calcs are done with Int/int anyway
20:26 timotimo mhm
20:26 timotimo also, we're not in reach of having even int8 arrays with 2**64 slots
20:29 jnthn m: say 2 ** 63
20:29 camelia rakudo-moar 3ca0f8: OUTPUT«9223372036854775808␤»
20:30 timotimo m: say (2 ** 63) / (1024 * 1024 * 1024 * 1024), " terabyte"
20:30 camelia rakudo-moar 3ca0f8: OUTPUT«8388608 terabyte␤»
20:30 timotimo m: say (2 ** 63) / (1024 * 1024 * 1024 * 1024 * 1024), " petabyte"
20:30 camelia rakudo-moar 3ca0f8: OUTPUT«8192 petabyte␤»
20:38 cygx_ joined #perl6-dev
20:40 * cygx_ put in his own 2 cent: https://www.reddit.com/r/perl/comments/557m4k/any_new_perl_6_books/d8jlxji
20:42 timotimo jnthn: will we move toward using Uni for path names and such?
20:43 jnthn timotimo: Doubt it
20:44 cygx_ what's the perl6 story on how to handle non-normalized filenames?
20:44 cygx_ or rther, what is it supposed to be :p
20:45 jnthn cygx_: The utf8-c8 encoding is meant to play that role by mapping things that would either fail to decode or be changed by normalization to synthetic codepoints, then back.
20:47 jnthn Moar already uses it in the applicable places
20:47 timotimo ah, so we'll get support for normalization changes there
20:47 jnthn Yeah
20:47 jnthn The thing already needs a doing over
20:47 cygx_ .oO(what about utf-16-ish things like windows)
20:48 timotimo windows has unicode awareness built into the FS
20:48 timotimo so we don't have that problem there, right?
20:48 timotimo like, you can't have a file ä.txt and a file ä.txt (with the other thing) as two separate files in the same dir?
20:49 jnthn .oO(WideCharToMultiByte/MultiByteToWideChar)
20:50 geekosaur yes, it normalizes. So does OS X HFS+
20:51 cygx_ geekosaur: according to a 2011 stackoverflow answer, Windows at the very least did not use to...
20:52 cygx_ "the file system treats path and file names as an opaque sequence of WCHARs."
20:53 cygx_ from https://msdn.microsoft.com/en-us/library/windows/desktop/aa365247(v=vs.85).aspx
20:57 geekosaur the complete version of that sentence (including the initial part) makes no sense though
20:57 geekosaur "There is no need to perform any Unicode normalization on path and file name strings for use by the Windows file I/O API functions" can only be true if it *does* normalize
20:59 cygx_ the formulation is misleading, but the rest of the paragraph clarifies it
21:00 cygx_ you do not 'need' to normalize because all strings are non-normalized
21:00 cygx_ you 'only' have to treat them as opaque
21:01 geekosaur soooo, windows acts like native unicode except when it doesn't and introduces all the problems that unnormalized names give you. wonder how many people have stolen data that way so far. (also wonder how many windows programs explode if you have both versions of a compose-able letter)
21:10 Ven_ joined #perl6-dev
21:11 dalek nqp: 916b2fd | FROGGS++ | tools/build/MOAR_REVISION:
21:11 dalek nqp: bump moar for nativecall improvements
21:11 dalek nqp: review: https://github.com/perl6/nqp/commit/916b2fdb94
21:12 dalek rakudo/nom: 677db95 | FROGGS++ | t/04-nativecall/12-sizeof. (2 files):
21:12 dalek rakudo/nom: add more tests for nativesizeof()
21:12 dalek rakudo/nom: review: https://github.com/rakudo/rakudo/commit/677db95b07
21:12 dalek rakudo/nom: 6977b87 | FROGGS++ | tools/build/NQP_REVISION:
21:12 dalek rakudo/nom: bump nqp/moar for nativecall improvements
21:12 dalek rakudo/nom: review: https://github.com/rakudo/rakudo/commit/6977b87413
21:36 lizmat m: 42 R= my $a; say $a   # wheeee  :-)
21:36 camelia rakudo-moar 6977b8: OUTPUT«42␤»
22:04 FROGGS joined #perl6-dev
23:21 dalek roast: 7d6ddc6 | MasterDuke17++ | S12-class/attributes.t:
23:21 dalek roast: Test .gist for attribute types
23:21 dalek roast:
23:21 dalek roast: Requires https://github.com/rakudo/rakudo/pull/899
23:21 dalek roast:
23:21 dalek roast: Tests for RT #129830
23:21 dalek roast: review: https://github.com/perl6/roast/commit/7d6ddc65da
23:21 synopsebot6 Link:  https://rt.perl.org/rt3//Public/Bug/Display.html?id=129830
23:48 Zoffix joined #perl6-dev
23:48 yoleaux2 joined #perl6-dev
23:49 buggable joined #perl6-dev
23:49 NeuralAnomaly joined #perl6-dev
23:49 Zoffix .tell psch we do have the .tell bot. It just got stuck behind the netsplit
23:49 yoleaux2 Zoffix: I'll pass your message to psch.

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