It is not well thought-out, delete the repo

[AlexDaniel]

I know that this repo is old, but it was mentioned in a recent discussion so that's why I'm here.

There are two points in the document and both of them are either wrong or incomplete.

“Do not base your design on junctions and autothreading”

debugging code with junctions is hard

???

and often confusing to read

???

“Use whitespace around infix operators”

5 .. 10? 2 ** 32? base 255 : 16? Maybe even 42 . sqrt? That's not how people write these things (normally), and I don't see a convincing argument for a style guide to mandate these variants. That's without even mentioning the huge list of cases where having no whitespace can't cause any issue (e.g. all non-texas infix ops).

Having whitespace around some infix ops is good. But “It is therefore recommended to always use whitespace on both side of an infix operator.” is a statement that is too strong. And I wouldn't want want to see a huge list of exceptions there.

o/

[AlexDaniel]

By the way, we have a list of recommendations that achieves a much better goal: https://docs.perl6.org/language/traps (also some pending sections).

[AlexDaniel]

In fact, maybe we can even add “Infix operators without whitespace” point there.

[AlexDaniel]

Ah, we already have it. It does not mention 1<2 case, which we now have an issue for: Raku/doc#1481

[AlexDaniel]

FWIW another option is to give proper explanations. For example: https://irclog.perlgeek.de/perl6/2017-10-22#i_15336776