At this point, Go would just see macros as automatically called code generation, which leads to an unpredictable speed reduction in compile times especially wit

At this point, Go would just see macros as automatically called code generation, which leads to an unpredictable speed reduction in compile times especially with large dependency trees. Slowing down compile times at any noticeable level is probably a non-starter based on language goals.