> Do we *need* a new file for testing new macros? > So far, everything went to test_common.c.
I'll move into test_common.c. I'll keep independent tests that verify pointer types natively (existing tests use uintptr_t).
> Do we *need* a new file for testing new macros? > So far, everything went to test_common.c.
I'll move into test_common.c. I'll keep independent tests that verify pointer types natively (existing tests use uintptr_t).