Hi Joseph, On Tue, Oct 14, 2025 at 09:29:13PM +0000, Joseph Myers wrote: > On Tue, 14 Oct 2025, Alejandro Colomar wrote: > > > > feature is "like N3628 but with changes X and Y" it needs to be stated > > > explicitly. > > > > Yep. I'll instead send a new N document removing bool from the > > supported types, and then refer to that. > > As a matter of language design, I think it's better to include bool rather > than exclude it.
_Maxof and _Minof are already niche, being useful for implementing type-generic integer macros that work well for integers of any width (e.g, u64, u32, 16, u8). Because bool is entirely different from the other regular integer types, and has entirely different rules, it's not a useful overload in generic macros, and thus I don't conceive useful uses of _Maxof and _Minof with it. When I see a valid use of _Maxof and/or _Minof with bool, I'll believe it. Also, it's easy to extend features, but not so much to narrow them. Thus, I find it better (safer) to exclude it, at least initially. I welcome anyone interested in supporting bool to show a valid use case for it. I prefer to be cautious by default. Have a lovely night! Alex -- <https://www.alejandro-colomar.es> Use port 80 (that is, <...:80/>).
signature.asc
Description: PGP signature
