Márton Polgár

> A different way to phase this issue would be "next, last, and redo should have lexical scope rather than dynamic scope" I don't think this reflects the `Block` vs...

> IMO having this behavior differ between Blocks and Subs would be highly confusing. Well, what can I say, I think this is _the whole point `Block`s exist in the...

> The other point is that its semantics greatly differs from that of next and its "kins". Well, does it? Are they not all pragmatisms over structural code, sort of...

A couple of ideas: - an "adverb" to control multi-level classification; either opt-in or opt-out - draw a distinction using containers (or conceptually rather itemization) - draw a distinction using...

@zag maybe this could be interesting for you as well

> The only downside I see, one that I suspect Larry did not foresee, is that someone influential on the official documentation was of like mind to you and avoided...

Long story short, I also lean towards giving up on this and letting user space handle it. I have admittedly not spent a lot of research with the parts of...

@crazywhalecc this probably doesn't have very high priority but still, considering that the `doctor` command can somehow account for environmental peculiarities, it would make sense that `spc` does something similar...

Pretty sure JSON does not know complex numbers so there is no point in "jsonifying" them. This module is not a serializer that uses JSON format under the hood -...

There was a new attempt to create an LSP for Raku not so long ago: https://github.com/bscan/RakuNavigator. Also I think we've had some constructive discussion about how to progress at https://github.com/Raku/atom-language-perl6/issues/90