🦋 Welcome to the IRC channel of the core developers of the Raku Programming Language (raku.org #rakulang). This channel is logged for the purpose of history keeping about its development | evalbot usage: 'm: say 3;' or /msg camelia m: ... | Logs available at irclogs.raku.org/raku-dev/live.html | For MoarVM see #moarvm
Set by lizmat on 8 June 2022.
Geth rakudo/main: eedc165f44 | (Elizabeth Mattijsen)++ | 6 files
RakuAST: several fixes and preparations

  - indentation is determined by the last seen =doc statement, *not*
   by the initial =begin
  - keep opener / closer with RakuAST::Doc::Markup object, for (de)parsing
  - adjust stringification of ::Markup accordingly
  - don't create RakuAST::Doc::Paragraph objects for a simple string
  - various fixes with LegacyPodification, e.g. support for V<> and
   not rendering a bare newline at the end		 17:23
lizmat still 803
m: dd $=pod[0].contents[0].contents[0]␤=foo B< <bar> > 17:28
camelia FormattingCode @!contents = Pod::FormattingCode.new(type => "B", meta => [], config => {}, contents => ["<bar> "])
lizmat that's expected, apart from having the leading whitespace having been trimmed 17:29
m: dd $=pod[0].contents[0].contents[0]␤=foo B« «bar» »
camelia FormattingCode @!contents = Pod::FormattingCode.new(type => "B", meta => [], config => {}, contents => ["«bar"])
lizmat so why is the » not part of the markup? It was when using <bar> ? 17:30
m: dd $=pod[0].contents[0].contents[0]␤=foo B< «bar» >
camelia FormattingCode @!contents = Pod::FormattingCode.new(type => "B", meta => [], config => {}, contents => ["«bar» "])
lizmat and here it's back again 17:31
[Coke] misparse, i guess 18:06
guessing regex is overeager 18:07
[Coke] grammar's pod_formatting_code Has some confusing logic for guillemet versus angle bracket 18:30
lizmat yeah, not going to look at that 18:32
I've taken a more reverse engineering approach to this 18:33
[Coke] Ah, just going to do it write in the AST and not worry about this? 18:49
+1 if so 18:50
Geth rakudo/main: c10767e533 | (Stefan Seifert)++ | 2 files
RakuAST: fix fallback resolver looking in wrong scopes

We need to preserve the state of the resolver where the code object actually sits in the tree, not when dynamic compilation is called.		 19:23
nine And yet more workarounds for dynamic compilation. Wonder if they will be enough or if we will be forced to re-think a lot of this at some point. 19:24
lizmat 805! 22:15
japhb \o/ 22:16

Powered by Cro and the Raku® Programming Language.

Please report any issues / comments / feature requests as an issue on App::Raku::Log.

Thank you!