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 1 November 2017.
02:57 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
07:16 domidumont joined 07:35 domidumont joined 07:37 domidumont joined 12:09 llfourn joined 14:10 Tom_Leg joined 14:21 stmuk_ joined 14:39 perlpilot joined 15:21 japhb joined 18:27 domidumont joined
ranguard stopping PSIXDISTS uploads 20:37
been told perl 6 module authors are now doing it themselves :)
*cheer* btw :) 20:43
ugexe thanks for your part in that ranguard 21:03
ranguard np, glad p6 infra is growing up ;) 21:08
ugexe nine: what do you think about the idea of add a .long-name() to CU::DS? It would be the same as CU::Distribution.Str, which differs from CU::DS.Str() in that it includes :ver<*> for non-specified version (and auth, api). This is intended to make `return %!loaded{~$spec} if %!loaded{~$spec}; (find a matching dist/ver) return %!loaded{~$spec} //= $dist;` (how we do basic caching) always load the same 21:41
version for `use Foo` and `use Foo:ver<*>`
i can put it in a small utility sub as well, but where should i put it for CUR::FS and CURI? (and probably CUR::Distribution.Str) 21:44
`use Test;` `use Test:ver("");` `use Test:ver<*>;` 22:08
i imagine two of those should be equal, with the third being debatable 22:10