Daniel Sockwell

(I was the person @StuartJMackintosh quoted above) That change to the README looks good to me.

Thanks for the quick reply and explanation. Answers to your questions are below: > what sort of a computer is it, The computer I'm connecting to is a System76 Galago...

We discussed this at today's RSC meeting and I'll reach out to others at YAS. Very sorry that I missed these notifications! I have GitHub set watch the Rakudo repo...

> In principle, I'm for option 1. But the main problem is that of priorities. I agree 100%. That said – at least speaking personally – it can be significantly...

> Also, we always need to take into account Roast; if it's not in roast, it's simply not spec and behavior might change at any time. That does not mean...

I'm not sure I'm communicating my point clearly. In my view, the question we're trying to figure out is how to document something (not what to document), so we might...

> If this is not a trick question, of course I agree. Definitely not a trick question. No tricks here! > [We should document methods] exactly where they are declared,...

After an **extremely** interesting an mind-expanding conversation with @coke in the IRC channel ([lines 529-609](https://colabti.org/irclogger/irclogger_log/raku?date=2020-08-21#l529)), I've come to believe that I was fundamentally mistaken above, and no longer believe that...

See also the (brief) discussion of Twigils in the design docs https://design.raku.org/S02.html#Twigils

@treyharris You bring up some really good points. Here's my perspective as someone who came to Raku without Perl experience but who still remembers being tripped up by that distinction:...