Sure as hell isn't making it a better place for Germans or anyone else in targeted nations.

If that's the case, there must be a hell of a lot of unconvicted white murderers to make up for the 7:1 disproportion.

Option has been around for a while as boost::optional or now std::experimental::optional. Result is coming and has a reference implementation as boost::expected. There's also a type-erased option type, "any".

They're quite nice, especially with a few trivial additions for ergonomics.

Yup, except you lost me as soon as you said "boost". I enjoy my fast compile speeds very much. :)

For the record, KeePass added header authentication after (thanks to) this paper.

Also, Dominik responded to claims made in a (unfounded) post here: https://news.ycombinator.com/item?id=9727297 with a quick blurb: http://keepass.info/help/kb/sec_issues.html

I think KeePass with the key file option (not readable by user accounts, run KP as admin) is the best solution on Windows I've found.

More details here:

http://keepass.info/help/kb/db_headerauth_upg.html

This isn't about any of that. Any classes you would apply this technique to already have the desired semantics. The rule of zero just argues that you should not write copy/move/destructor functions outside of dedicated resource mananging classes, so that you can write other classes with zero special member functions (other than the main constructors).

Types-as-variables is a very good insight. When I'd write C++ function headers where I could omit parameter names without losing any clarity, it'd feel really nice, but the implication never rose to consciousness.

I started one a while ago, but I became fascinated by the "middle end" and bought a compiler textbook. Now I have SSA optmizations but no strings still.