Daniel Sockwell
Daniel Sockwell
I just opened Raku/problem-solving#390 to help resolve this issue. Please note that, as I mention in that issue, the problem is **not** actually with `rule`s specifically but rather with `:sigspace`...
After looking at the S06 section @raiph linked, I see the merit of the `` syntax. For example (if implemented), writing ` would be a handy way to match either...
I looked at the diff before submitting the PR and I believe the issue is due to a bug in the non-RakuAST --doc relating to whitespace Sep 30, 2023 8:21:03...
@lizmat wrote: > I don't think this applies to whatever-currying, but more to what `.assuming` does? But the point is that whatever-priming/currying does exactly the same thing as `.assuming`. Here...
> Except that the first creates a `Callable` **out of thin air** No it doesn't. Both create a `Callable` by wrapping `&infix:`, just with different spelling. > For instance, what...
> Except that method calls are late bound, so that won't fly. I see what you mean; `Str.^lookup('tc').assuming()` always calls the `Str` method, whereas `*.tc` will call the first `tc`...
@2colours wrote: > My point is specifically that it might cause confusion if this change happens without people really knowing about it, and that in general it almost feels more...
It also looks like none of the atomic operators are documented in /language/operators. Here's the full list (taken from /language/unicode_ascii in case anyone feels like taking a crack at adding...
Cross references: * Raku/problem-solving#97 * rakudo/rakudo#5430 * Raku/doc#4389
Proposed solution: Raku v6.e should provide the following Unicode operators: | Symbol| Code | Equivalent to | |-----------|----------|----------| | → | U+2192 | -> | | ⟶ | U+27F6 |...