Perl 6 - the future is here, just unevenly distributed

IRC log for #perl6-toolchain, 2017-08-11

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

All times shown according to UTC.

Time Nick Message
01:52 ilbot3 joined #perl6-toolchain
01:52 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
02:19 sivoais joined #perl6-toolchain
02:19 sjn joined #perl6-toolchain
02:20 lizmat joined #perl6-toolchain
02:20 ranguard joined #perl6-toolchain
02:29 camelia joined #perl6-toolchain
02:48 ugexe https://github.com/sergot/http-useragent/blob/a7e317c78f215844a86159d11b99f065487fe716/lib/HTTP/UserAgent.pm6#L30
02:48 ribasushi joined #perl6-toolchain
02:48 ugexe https://github.com/sergot/http-useragent/blob/a7e317c78f215844a86159d11b99f065487fe716/lib/HTTP/Response.pm6#L13
02:49 ugexe X::HTTP::Response is declared in both modules, one inherits from Exception and one inherits from X::HTTP is Exception
02:56 ugexe But again this works for just `use HTTP::UserAgent`. once its `use Bailador; use HTTP::UserAgent;` this becomes a problem. So what does Bailador bring to cause a problem? I see two interesting things: X:: namespace and ::Response namespace (both dists use these). I suspect one of these changes conditional outcomes in merge_globals (is_stub or =:=) to ultimately merge differently than without Bailador
03:00 ugexe im kinda just taking shots in the dark, but the stash difference with/without Bailador before merge failure has only 2 differences - :Bailador(X::Bailador) and :Template(X::Template) stash entries
03:01 ugexe but that bit might be irrelevant... i'm not totally sure its *exactly* the same spot
03:11 ugexe thats its. by removing X::HTTP::Response from HTTP::UserAgent it all loads fine. it looks like it was done like this to avoid circular dependency on base exception class X::HTTP (defined in HTTP::UserAgent, but would then need to be used in HTTP::Response which already is used by HTTP::UserAgent)
03:23 ugexe i wonder if its the X:: or ::Response from Bailador that causes it
07:03 lizmat joined #perl6-toolchain
07:38 lizmat joined #perl6-toolchain
07:49 lizmat joined #perl6-toolchain
09:00 lizmat joined #perl6-toolchain
09:18 lizmat joined #perl6-toolchain
09:39 lizmat joined #perl6-toolchain
10:10 lizmat joined #perl6-toolchain
10:32 lizmat joined #perl6-toolchain
11:34 lizmat joined #perl6-toolchain
11:41 nine I can't shake the feeling (and it's not more than that) that maybe the X namespace may be handled specially somewhere
12:19 tbrowder joined #perl6-toolchain
13:03 lizmat joined #perl6-toolchain
13:30 lizmat joined #perl6-toolchain
13:57 lizmat joined #perl6-toolchain
13:59 lizmat joined #perl6-toolchain
14:28 lizmat joined #perl6-toolchain
15:08 lizmat joined #perl6-toolchain
15:35 lizmat joined #perl6-toolchain
15:44 lizmat joined #perl6-toolchain
16:36 lizmat joined #perl6-toolchain
18:29 tadzik joined #perl6-toolchain
20:04 tadzik joined #perl6-toolchain
22:19 ugexe nine: https://gist.github.com/ugexe/f78c4218235fe2aa0f20955953f8263a this "fixes" the problem. but I imagine it breaks other things (despite passing spec test)
23:16 ugexe created as a workaround for https://irclog.perlgeek.de/perl6-toolchain/2017-08-10#i_14996577
23:19 ugexe maybe a good spot to put more debugging info at least
23:33 lizmat joined #perl6-toolchain

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