I recommend using https://regex101.com/

It explains all parts of your regex and highlights all matches in your example text. I usually add a comment to a regex101 playground if I use a regex in code.

Many people on feddit.de already do so

Since mastodon has no equivalent to lemmy’s communities, it can’t handle lemmy’s !community@instance links.

Communities are represented as a regular user on the mastodon side, if you mention a user (using @) on mastodon, it will be parsed as a markdown link on lemmy: [@lucy_idk](https://mastodon.world/@lucy_idk)

I think it wasn’t meant as a repost to this community. It was a post on mastodon that was picked up by lemmy because this community was credited:

Found by: @programmerhumor

https://htmx.org/

Just put

true = False
false = True

at the top of your files.

That’s what I love about Rust: many problems that would turn into runtime errors in other languages aren’t possible with its type system and the compiler catches them.

And we will be monitored too!

Type Annotations and other typing-related stuff are built into the language/standard library.

To get a real benefit you should use a static type checker like mypy.

Rust has pretty strong stability guarantees. Backwards incompatible changes are only made using “editions” where every compiler version supports all previous editions and editions are fully interoperable.

https://doc.rust-lang.org/stable/edition-guide/editions/index.html#what-are-editions

That’s why I like to include a comment with a link to an example on regex101.com.