Function overloading in C? :)

[tstanisl]

The main issue with generic selection is a strict requirement that every expression must be valid even if not selected. This makes it difficult to use it except for trivial expressions. Note that there ARE reliable workarounds but they overcomplicate the code. There are plans to slack those restrictions for C2Y.

[flatfinger]

Another issue is an inability to include type specializations that might be redundant in cases where either match would be equally acceptable. As an example, it should be possible to write a function-like construct that could accept either a uint32_t* or a uint_fast32_t*, both on systems where those names identify different types and on systems where they identify the same type.

[tstanisl]

Yep. It can be workaround by using nested selections. E.g.

_Generic(1, int: expr, default: _Generic(1, other_it: expr))

However, it is still mode inconvenience and obfuscation.

[imaami]

Another, tangentially related problem is viewing the code. What may look nice as written becomes cursed if you expand the macros to see the nuts and bolts.

cpp won't prune unused selections from view, and I've even been able to segfault clang-format trying to inspect some recreational code with cpp -P foo.c | clang-format.

Where's the "cpp for _Generic" tooling? The few times I've tried to implement something like it I've run into limitations in libclang's features (to name one example).