1,142 karma · joined April 8, 2010
Am I missing something?
If I had to define it, I would go with runtime-only, but I could see the other way too.
I suppose a difference is that they use unaffiliated parties to send the complaint, instead of contacting the authority directly.
It's possible to read "hunter2" from /dev/random.
To infer entropy from a single password, the best you can do is to see if it falls within the domain of some known, low-entropy systems. This works ok in practice, but is very far from perfect.
One particularly nice thing about it is that it's completely optional sugar over a lispy "FullForm" syntax, and it's easy to convert between the two.
I'd encourage everyone to play with it, but it's sadly non-free.
If a compiler is certain there's UB should it format the developer's hard drive immediately, or does it have to wait until the program is run before formatting to be standards compliant?
On a more serious level, should it emit a warning? If it knows UB is reached, a warning sounds reasonable, but it's pretty rare that a compiler is 100% certain something is reached, and that analysis is probably not worth the cost.