Pharo 4 will define ifTrue: on non-booleans, adding truthiness to Pharo (for better or worse): http://t.co/A7wNcGVqa9
miniblog.
Related Posts
I'm slightly surprised that Rust has implemented the Default trait for booleans: https://doc.rust-lang.org/src/core/default.rs.html#205
The default is false, but it feels very arbitrary. Maybe it makes more sense next to integers, where the default value is 0.
I've been learning some CMake, and it's a weird language. "ON" is used for booleans, it puts code in .txt files, but it still has a lispy macro system.
I suspect the vast majority of people (including me) learn CMake from a large preexisting build. That will bias impressions.
Whilst nil and t are rather strange as booleans, they're wonderfully easy to type.
I've finally relented and written a yasnippet for Python because True and False are just too many keystrokes.