|
Fire is step THREE! | github.com/perl6/toolchain-bikeshed | Channel logs: irclog.perlgeek.de/perl6-toolchain/today | useful prior art: metacpan.org/pod/CPAN::Meta::Spec Set by moderator on 18 April 2017. |
|||
|
01:49
ilbot3 joined
|
|||
| moderator | Fire is step THREE! | github.com/perl6/toolchain-bikeshed | Channel logs: irclog.perlgeek.de/perl6-toolchain/today | useful prior art: metacpan.org/pod/CPAN::Meta::Spec | ||
|
06:10
domidumont joined
06:35
domidumont joined
06:41
domidumont joined
08:32
domidumont joined
08:41
domidumont joined
08:56
domidumont joined
12:31
domidumont joined
12:43
domidumont joined
|
|||
| nine | Just pushed the first half of replacing precomp file time stamp checks by proper checksums :) | 15:08 | |
| [Coke] | nine++ | 16:53 | |
| 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:10 | |
| I'm probably phrasing that question poorly... ribasushi ^ | 17:11 | ||
| nine | Well the object is a Foo:ver<2>, so it will behave that way | 17:27 | |
| 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. | 17:33 | ||
|
18:37
domidumont joined
|
|||