[lifthrasiir]

The concrete problem that the kernel is facing is an exponential growth of macro expansion. Any current solution, safe or not in terms of re-evaluation, needs at least two copies of both arguments to be expanded [1], so expressions like `min(min(a, b), c)` will expand some arguments four times. The growth factor would be much larger than two if the definition wasn't carefully designed to avoid such cases.

[1] `_Generic` also requires at least two because you need one copy to select the generic implementation and another to call it. C23 `typeof` (or the equivalent GNU extension) allows for a compact type tuple matching:

    inline static int max_int(int x, int y) { return x > y ? x : y; }
    inline static unsigned max_uint(unsigned x, unsigned y) { return x > y ? x : y; }
    /* ... */

    #define MAX(a, b) (_Generic( \
        (void (*)(typeof(a), typeof(b))) NULL, \
        void (*)(int, int): max_int, \
        void (*)(unsigned, unsigned): max_uint, \
        /* ... */ \
        default: max_type_error \
    ) (a, b))