Skip to main content
Code Golf

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

5
  • \$\begingroup\$ This solution is incorrect. \r by itself is allowed in regular comments (however not doc-comments). \$\endgroup\$ Commented Nov 4, 2021 at 13:03
  • \$\begingroup\$ @KonradBorowski fixed, an update to rust made that strategy completely obsolete. \$\endgroup\$ Commented Nov 4, 2021 at 17:04
  • \$\begingroup\$ "Every individual character in your submission must be admissible in a legal program; that is, you can't just use a character which is always rejected." If this is only a single U+202A, wouldn't this violate that rule? \$\endgroup\$ Commented Nov 4, 2021 at 21:05
  • 1
    \$\begingroup\$ @Bbrk24 should be fixed- after a little digging, I figured out that if you try hard enough you can put U+202A inside your code. \$\endgroup\$ Commented Nov 4, 2021 at 22:05
  • 1
    \$\begingroup\$ I was going to say that it's possible to allow a lint with #![allow(text_direction_codepoint_in_comment)], but as it happens, in Rust 1.56.1 this lint was incorrectly declared and as such the compiler is not aware of it, see github.com/rust-lang/rust/issues/90614. Due to that, this is a valid solution. \$\endgroup\$ Commented Nov 5, 2021 at 15:10