|
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 9 August 2017. |
|||
| ugexe | seems it might be messing up trying `HTTP::Response::X::HTTP::Response =:= HTTP::UserAgent::X::HTTP::Response`, but why do these two separate names get installed? | 00:48 | |
|
01:52
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 | ||
|
03:44
stmuk joined
06:16
lizmat joined
06:22
lizmat_ joined
06:38
lizmat joined
09:12
lizmat joined
10:12
lizmat_ joined
10:16
lizmat joined
10:31
lizmat joined
11:48
lizmat joined
12:41
lizmat joined
13:12
lizmat joined
13:34
lizmat joined
13:37
lizmat joined
14:35
lizmat joined
|
|||
| ugexe | nine: so what does it mean when (X::HTTP){Response}.perl.say is 'HTTP::UserAgent::X::HTTP::Response' and (X::HTTP){Response}.WHO.say is 'HTTP::Response::X::HTTP::Response'? | 15:52 | |
| X::HTTP::Response is declared in HTTP::Response. and HTTP::Response is used by HTTP::UserAgent. | 15:53 | ||
| nine | ugexe: that sounds really scary | 16:24 | |
| ugexe | i thought so as well. although even scarier is that `use Bailador` somehow causes it | 16:31 | |
| right now im kinda stuck on not being able to dump github.com/rakudo/rakudo/blob/5e8d...r.nqp#L265 | 16:32 | ||
| i basically want to dump all the symbols as they change so I can do a diff between `use Bailador; use HTTP::UserAgent;` and `use HTTP::UserAgent` | |||
| nine | Yes debugging in nqp is not exactly fun | 16:34 | |
| ugexe | the HLL Compiler has a dumper, but I havent tried to access that inside ModuleLoader.nqp yet (or if its even possible) | 16:35 | |
| nine | You can always cheat by doing note nqp::hllizefor($hash, "perl6").gist;' | 16:36 | |
| ugexe | ah i'll try that | 16:38 | |
| nine | And $foo.HOW.name($foo) to get the type name | 16:39 | |
| ugexe | on a similar note, it would be nice if RAKUDO_MODULE_DEBUG had a way to get reproducable / diffable results | ||
| nine | We'd have to replace the PID with maybe a level counter | 16:40 | |
| ugexe | yeah, or just a flag that knows how to strip it (unless a level counter is needed) | 16:41 | |
| i suppose it would be | |||
| nine | It'd get kinda confusing without any differentiation :) | ||
| ugexe | if you are just diffing its not, which is why I glossed over it | 16:42 | |
| seems like levels would be better than pid anyway no? | 16:43 | ||
| nine | vimdiff does a good job at highlighting the changes though ;0 | ||
| probably yes | |||
| Oh, it also prints the time. But we could just remove that. | 16:45 | ||
| Patch coming up | 16:47 | ||
| ugexe | if I add `DEBUG(nqp::hllizefor($hash, "perl6").gist if $DEBUG` then it fails quickly with `Cannot look up attributes in a ... type object` | ||
| ... changes depending on how I invoke it | 16:48 | ||
| for instance: `Cannot look up attributes in a Bailador::Route::Prefix type object` | |||
|
16:55
lizmat joined
|
|||
| nine | I guess those classes just .gist badly :/ | 17:06 | |
| ugexe: pushed the reproducible RMD patch | 17:14 | ||
| ugexe | awesome | ||
| nine | My brane is not good for much this week, but a bit of string fiddling I can do :) | 17:21 | |
|
17:31
lizmat joined
17:51
lizmat joined
17:56
lizmat joined
21:22
lizmat joined
|
|||