4 ms·
You also have to supply alternatives to && || and not; that still leaves functions (e.g. filter) and constructors with Boolean parameters. Whether you're fighti
by mooism2 13y ago
You also have to supply alternatives to && || and not; that still leaves functions (e.g. filter) and constructors with Boolean parameters. Whether you're fighting the language or the standard library is a moot point: you're fighting it instead of working with it.
- eru 13y ago> You also have to supply alternatives to && || and not; that still leaves functions (e.g. filter) and constructors with Boolean parameters. There's some lifting approaches that construct those functions mostly automatically for you, as wrappers around the base functions on Booleans.