This seems like such an unergonomic language for developing financial programs, with hidden sharp edges.

eg. How on earth could you think it's OK to let you destroy (or permalock) coins through any mechanism other than a blatently clear semantic like DestroyCoins()? Accountants learned that lesson ages ago with the invention of double-entry bookkeeping.

Can any programmers in the space comment on whether and how newer languages improve on some of the gotchas?