[01:53] *** hulk joined [01:54] *** kylese left [02:15] *** hulk left [02:15] *** kylese joined [03:19] *** lichtkind_ joined [03:22] *** lichtkind__ left [03:24] *** japhb left [05:04] *** vrurg_ joined [05:07] *** vrurg left [05:40] *** belluzj joined [05:41] *** japhb joined [05:45] *** belluzj left [07:58] *** kylese left [08:00] *** kylese joined [08:17] *** Sgeo_ left [09:13] Is there a way to get rakuast to keep comments? [09:14] I see declarator docs but not trailing comments [09:16] well, comments are comments :-) [09:16] but no, not at the moment... [09:16] Trying to write a linter :D [09:17] with formatter [09:17] although the origin information of nodes created by the Raku grammar *should* have enough information to trace back in $?SOURCE, and thus be able to reconstruct commets [09:18] *comments [09:18] m: say $?SOURCE [09:18] rakudo-moar e17a1d43b: OUTPUT: «say $?SOURCE␤» [09:18] Will take a look, thanks. [09:18] m: say $?SOURCE # with comments [09:19] rakudo-moar e17a1d43b: OUTPUT: «say $?SOURCE # with comments␤» [09:20] *** abraxxa joined [09:25] *** abraxxa left [09:27] *** abraxxa joined [11:33] *** belluzj joined [11:45] *** ckfl3266 left [12:07] *** Geth left [12:07] *** Geth joined [12:22] *** belluzj left [14:27] https://github.com/ugexe/Raku-rakufmt [14:28] just a toy demonstration, but it handles comments [14:29] to be clear i dont have plans to seriously continue that program, i just needed it to prove out the stuff for tracking spaces in rakuast so a real linter/formatter could [14:29] s/tracking spaces/tracking comments and whitespaces/ [15:40] *** Terifto joined [15:54] Hello! What is currently the best way to debug a Raku program? The Raku website recommends `use trace`, but that makes the program crash where it didn’t before. Raku-debug asks for `Debugger::UI::CommandLine`, but it won’t precompile, and has apparently been superseded by `App::MoarVM::Debug`. But the latter doesn’t find its libraries when [15:54] installed from zef using rakubrew; I got it to run by installing manually, but it’s entirely unresponsive. Is there a more reliable approach (other than inserting print/say statements in the code), or should I try harder at making one of these work? [16:02] there's a "repl" sub that puts you in the REPL, that you can sprinkle in your code [16:02] App::MoarVM::Debug should work [16:06] I’m not sure where exactly the program I’m trying to debug gets stuck, so a way to follow the program without knowing exactly where would be useful. (The repl sub sounds neat, though!) [16:08] If I’m having trouble getting App::MoarVM::Debug to run, should I perhaps file a bug with it, or with zef, or with rakubrew? (I guess try one of those and they’ll send me elsewhere if it’s not their problem?) [16:11] <[Coke]> if you can't run zef, ping rakubrew. if you can't install the module, ping zef. If you can run the module but it's not doing what you think/want, ping the module [16:12] <[Coke]> You can also throw your session in a gist and we can look at it for something fixable. [16:12] <[Coke]> Is the actual program that's hanging in git somewhere? [16:20] Oh, I think I found the issue. The App::MoarVM::Debug version was updated to 0.3, but the included scripts are still trying to use version 0.2. [16:22] ah? [16:23] <[Coke]> ... that shouldn't be happening. [16:23] ah, oops,. that's non me [16:23] *on [16:23] <[Coke]> Are you shooting yourself in the foot, somehow? [16:23] <[Coke]> oh, or it could be liz's fault, I guess. :) [16:26] new version on its way to the ecosystem now [16:26] Terifto++ for figuring out the issue [16:26] dinner& [16:26] Oh, that was quick. Have a good meal. ^ ^ [16:52] *** lizmat left [16:59] *** lizmat joined [17:19] *** Sgeo joined [17:22] *** human-blip left [17:24] *** human-blip joined [17:40] *** Romanson joined [18:00] *** cleo joined [18:06] *** swaggboi left [18:31] *** swaggboi joined [18:41] *** Terifto left [19:17] *** abraxxa left [20:09] *** Romanson left [21:11] *** eseyman left [21:12] *** manu_ joined [21:12] *** manu_ is now known as eseyman