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.
01:49 ilbot3 joined 08:27 cog_ joined 10:04 cog_ joined 11:05 cog_ joined 11:57 Ven`` joined
Ven`` coming back to what you said, masak , a few weeks ago 11:58
"macro-expanded code is always synthetic" -> is that also true for spliced-in values?
I know scalac gets confused by its own mechanism for synthetic (in that it "forgets", kinda like Perl 5 with int/str)
I'm not sure the term "replica" is useful, splicing values into a quasi is somewhat like... instantiation? 11:59
masak no, spliced-in values can be organic (if they came in as parameters which were ultimately parsed macro arguments or operands) or synthetic (sometimes when the macro made them) 19:44
or a mix of the two
I'm less enthused about the "replica" terminology now. but I'm not keen on "instantiate" either. that term is a bit overloaded already, and kind of nabbed by OOP. 19:46
in other news: Q::Expr::StatementListAdapter will soon become Q::Expr::BlockAdapter 19:49
...because code-that-has-been-expanded-in needs a block-like container to hold declarations etc. so that these don't leak out 19:50
this is currently blocking infix:<ff> and family 19:51