And `unsafe` with `yolo`.

`sus` fits with unsafe better I think.

Currently the term "unsafe" is overloaded, as both the keyword used to mark definitions of things that require manual verification, and as the keyword used to mark a block to acknowledge that such verification has been done.

The correct approach is obviously to separate these two terms, and use "sus" to mark items that require verification, and "yolo" to mark that such verification has been done. Or:

    sus fn dangerous() { ... }
    
    yolo { dangerous() } // can only call dangerous inside a yolo block

pog

This is getting into Lolcode territory.

I HAZ A var ITZ A BUKKIT OF YARN

also three letter shorter, so a definite improvement.

Change panic! to yikes! when?

panic! should just become Panik

'unsafe' should be 'problematic'

or ‘prophylactic’…

if/else with consider/tho

assert with fr

I do not think we can trust a computer to decide whether something is true or false. These kinds of august deliberations are best left to the new Disinformation Governance Board!

All programs contain bugs and cosmic rays can flip bits at any time so it's nonsensical to trust boolean expressions. Therefore we should rename true/false to likely/unlikely.

literally/idk