From @masak

<jnthn> rakudo​: sub infix​:<ö>($x, $y) { say "flyyy" }; (1,2,3) »ö« (4,5,6)
<p6eval> rakudo 612bcf​: OUTPUT«Statement not terminated properly at
line 1, near "\x{bb}\x{f6}\x{ab} (4,5,6" [...]
<jnthn> aww.
<masak> is that a new bug?
<jnthn> Yes. No.
<moritz_> jnthn​: I think meta-ops are pre-generated
<masak> I mean, apart from being a known butterfly.
<jnthn> (Can't parse unicode hypers is known.)
<masak> ok.
<jnthn> But as moritz_ said, we don't handle generating meta-op forms yet.
<jnthn> For user defined ops.
<pmichaud> ....but we might be able to do so.
<moritz_> aka it's a "todo bug" ;-)
<jnthn> Oh, I'm sure we can.
<jnthn> It's just whether it's worth hacking it in now, or waiting for
when we can parse them the more STD-ish way, if that's teh plan.
* masak submits TODO bug

From @jnthn

On Thu May 14 09​:23​:14 2009, masak wrote​:

<jnthn> rakudo​: sub infix​:<ö>($x, $y) { say "flyyy" }; (1,2,3) »ö« (4,5,6)
<p6eval> rakudo 612bcf​: OUTPUT«Statement not terminated properly at
line 1, near "\x{bb}\x{f6}\x{ab} (4,5,6" [...]
<jnthn> aww.
<masak> is that a new bug?
<jnthn> Yes. No.
<moritz_> jnthn​: I think meta-ops are pre-generated
<masak> I mean, apart from being a known butterfly.
<jnthn> (Can't parse unicode hypers is known.)
<masak> ok.
<jnthn> But as moritz_ said, we don't handle generating meta-op forms yet.
<jnthn> For user defined ops.
<pmichaud> ....but we might be able to do so.
<moritz_> aka it's a "todo bug" ;-)
<jnthn> Oh, I'm sure we can.
<jnthn> It's just whether it's worth hacking it in now, or waiting for
when we can parse them the more STD-ish way, if that's teh plan.
* masak submits TODO bug

Implemented in git 6381427. Also added basic spectests in the new
S13-overloading/metaoperators.t (feel free to review/add to it, anyone).

Thanks,

Jonathan

The RT System itself - Status changed from 'new' to 'open'

@jnthn - Status changed from 'open' to 'resolved'