Hi
On 4/10/24 00:12, Larry Garfield wrote:
I feel the same. Adding an enum for each binary parameter that is
semantically true and false feels quite unwieldy with how class / enums
/ interfaces are currently organized in the namespace hierarchy.
Point of order: This parameter is *not* semantically true and false. It is
semantically either/or, and we kinda twist sideways to make it look like
true/false if we squint. That's actually pretty common in the current stdlib,
though it's not a good approach. Hence why I asked about an enum. I wouldn't
expect it to be single-function, though, but to be applicable for multiple
functions. (I did not go looking to see if such functions exist.)
Whoops, I accidentally a word in that paragraph, thank you.
It should have read "each binary parameter that is NOT semantically true
and false".
Best regards
Tim Düsterhus
