6macros: discussing the finer points of Perl 6 macros, Qtrees, and how to stay sane | irclog: irclog.perlgeek.de/6macros/today
Set by moderator on 28 July 2015.
06:21 pdcawley joined 08:00 pdcawley joined
sergot morning o/ 10:37
11:16 vendethiel joined 16:05 Ven joined
masak waves from a train 16:42
it's becoming increasingly clear that the next immediate focus should be quasis and unquotes. it's high time. 16:44
and there is much fun and unexpectedness in getting all that to work. 16:45
Ven yep. yay! 18:03
masak `quasi @ Q::Infix { + }`
what kind of Qtree would you expect back?
masak detrains, bbl 18:04
Ven dunno. I'm a bit busy right now, I'll try to look back later 18:08
19:06 FROGGS joined
masak sure, no problem 19:59
vendethiel: ping 21:26
vendethiel still helping some friends doing their projects
zzzz
masak aha. carry on, then :) 21:27
vendethiel because they didn't do anything during the week! 21:28
oh well.
masak slackers!
vendethiel quasi @... 22:17
well, obviously, I expect a "..." :P
I don't think we discussed "quasi @ ..." yet? 22:18
only as splicing syntax, iirc
masak ok 22:28
by default, the parser would see `quasi {` and go "alright, now I am inside a block, so the next thing I will see is a... statementlist"
this precludes generating a lot of useful AST types 22:29
or at least makes it a lot more difficult than it has to be
for example, if I wanted to make a quasi for a subroutine trait, I'd have to do something like `quasi { sub i_do_not_care_about_this() is foo(bar) {} }`, and then manually dig out the trait from the resulting quasi AST 22:30
solution: something like `quasi @ Q::Infix {`, which directly tells the parser which mode to place itself in as it enters the quasi block
all this is a solution to a problem which Lisp doesn't even have, since it's "modeless" in this sense 22:31
... 'night 22:34

Powered by Cro and the Raku® Programming Language.

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

Thank you!