Perl 6 - the future is here, just unevenly distributed

IRC log for #perl6-toolchain, 2017-04-21

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

All times shown according to UTC.

Time Nick Message
01:49 ilbot3 joined #perl6-toolchain
01:49 Topic for #perl6-toolchain is now Fire is step THREE! | https://github.com/perl6/toolchain-bikeshed | Channel logs: http://irclog.perlgeek.de/perl6-toolchain/today | useful prior art: https://metacpan.org/pod/CPAN::Meta::Spec
06:10 domidumont joined #perl6-toolchain
06:35 domidumont joined #perl6-toolchain
06:41 domidumont joined #perl6-toolchain
08:32 domidumont joined #perl6-toolchain
08:41 domidumont joined #perl6-toolchain
08:56 domidumont joined #perl6-toolchain
12:31 domidumont joined #perl6-toolchain
12:43 domidumont joined #perl6-toolchain
15:08 nine Just pushed the first half of replacing precomp file time stamp checks by proper checksums :)
16:53 [Coke] nine++
17:10 ugexe nine: how does lexical module loading work when passing say Foo:ver<2> object into something that eventually ends up in Foo:ver<1>? # a question I was asked when demoing lexical module loading earlier
17:11 ugexe I'm probably phrasing that question poorly... ribasushi ^
17:27 nine Well the object is a Foo:ver<2>, so it will behave that way
17:33 nine If you call methods on it, those will be Foo:ver<2>'s. If you pass it to Foo:ver<1> code, this code will have to cope with the differences between the versions.
18:37 domidumont joined #perl6-toolchain

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