[Pitch] Generalize `conformance` macros as `extension` macros

Ah good question, the compiler already handles this with conformance macros. Notice that the macro does not provide the name of the type it extends (both with conformance macros and with extension macros in this pitch) because the compiler binds the extension directly without doing name lookup of the extended type. The compiler also inserts the extension into the correct scope, not the potentially-nested scope where the macro is applied.

3 Likes