~bool deprecation

IMO, removing ~bool simply changes the nature of the confusion. Why remove ~, but leave +, -, * and /? For that matter, leaving & and | simply because they happen to behave as if bool was a full-fleged type of its own, while removing ~ because it doesn’t, feels weird to me.

I’d be a lot happier if this were part of a larger change to make bool a full-fledged boolean type. Either that, or I’d prefer to simply leave it alone.

I know practicality beats purity and all that, but this feels more like a perlish “do what I mean” (or in this case, “don’t do what I don’t mean” :slightly_smiling_face:)

17 Likes