Daniel Sockwell

@lizmat I'm slightly confused by your proposal. Right now, grammars and their matches (which are just grammars of the same type) have the following mro's: ```raku grammar G { token...

> The `$m` would be a `Match` object as before, nothing changes there. I'm still confused. Right now, if I have a grammar named `G`, each time one of `G`'s...

My ¢2 on this very interesting discussion: * On `Dateish` specifically: In theory, I like the idea of `ish` as a role marker – the problem is that Raku uses...

> On naming, the way one distinguishes a class from a role is by the > grammatical category of the word, NOT its spelling. A class has a NOUN >...

@duncand wrote: > A better language design is such that a data type is strictly defined as a set of values, full stop. If I'm understanding you correctly, this is...

> And we wrote raku.land for the Raku community. We wrote it because we saw the same problems that he saw with modules.raku.org. … raku.land is a community-driven project: it...

Thanks, that was my understanding as well. > the warp API is to be rewritten to have a better coverage of the websocket protocol That is exactly what I am...

> have you started on this already? My apologies for the delay in getting back to you on this. All I have done so far is the (very small) PR...

> Just remember that tungstenite always responds to pings automatically as long as you keep polling the stream or sending things in the sink. You should never manually answer the...

Expanding on this, this bug seems to be triggered by the infix form of function calling – all of the following also incorrectly produce "sink context" warnings: ```raku [[&say]] 'hello...