Michal Bozon

In Python, I'd do at least `set()` on provided recipient list. Should not be serious memory issue even though number of recipient is theoretically unlimited now.

Oh, for that singular change, it contains more commits than I wanted..

@Altai-man .. in fact, i would not say it's exactly "replaced", the original table "encouraged" use of character/codepoint, which is immediately normalized, see related closed rakudo issue linkd in this...

Well, I agree that this simple fix might not be the best way of updating the file, I'm unable to check if there are more characters to mention, and not...

@raiph English tongue is not my native one, I guess that "eg" is better *example* abbr. than "ex"; and thanks for making the title more clear.

I agree that ground footprint toggle would be more useful if being a global (per module) option too, as one probably wants to hide footprints for large constellations. (Btw, unfortunately,...

I was writing new issue request (but eventually got here): Raku docs don't seem to sufficiently reflect potentially unexpected Unicode normalization during Str construction. (I don't see it mentioned in...

@JJ it's OK, see red closed rakudo issue #4457 link above. Non-normalizad Unicode strings should be probably done like ```raku Uni(0x340).list eqv Uni(0x300).list # False ``` (direct Uni eqv'ing does...

Right. Here it's kind of mentioned: [language/traps](https://docs.raku.org/language/traps), section _All text is normalized by default_. Similar example might fit there.

Hi, another sample ``` #whateverable u: 〈 mykhal, U+3008 LEFT ANGLE BRACKET [Ps] (〈) ``` but it was actually ``` u: U+2329 mykhal, U+2329 LEFT-POINTING ANGLE BRACKET [Ps] (〈) ```...