Daniel Sockwell

> only now do I recognize you as the author of the "105 C++ Algorithms in 1 line of Raku" video I'm glad you liked the video and thanks for...

I'm sorry to see that this conversation took a turn and am locking it for now to give everyone a chance to take a breath. @2colours, you've had some very...

The two most obvious ways to address this issue are to either add a shorter synonym for `.assuming` or to create a new operator for partial application. However, both of...

> I'm not sure I'm a fan of partial composition in the form of `&sum o 1.` Could you say a bit more about what you dislike about that construction?...

You all make some excellent points and provide more than enough justification for proceeding slowly. However, I would like to push back on one point: > which means you probably...

Er, yes – you're absolutely right that I wasn't using the term "term position" correctly.  I probably should have said "as an operand (with most operators, including the method-call operator)"....

> I'm curious about why you posted this in problem-solving I posted this in problem solving to start a conversation about whether something that I view as a "problem" (or,...

> (however, that's probably because I don't think I've ever used `.assuming`). I also don't use `.assuming` all that often – but that's because I tend to just use a...

@jnthn finished the comment I quoted above by saying: > A further design issue in Rakudo today is that operator precedence properties are duplicated in multiple places: in the grammar...

> If you don't want that and leave the choice to the user and some other author uploads an incompatible module with the same short name - communicate. Tell that...