Macros are often too meta to read in context but code patterns are often repetitive.
Even if IDEs can generate the code, it must be maintained and is often skimmed (because generation was assumed even though it might have been tweaked or generated by a previous version of the IDE snippet).
Inheretance doesn’t work well for code re-use (conflates type hierarchies with code re-use, fragility of base class because you don’t know how it’s used)
How can literal code transclusion be used?
How does this relate to funtorial / generic programing (e.g. type syntax directed)
How does this relate to full on polymorphic programming
Macros are often too meta to read in context but code patterns are often repetitive.
Even if IDEs can generate the code, it must be maintained and is often skimmed (because generation was assumed even though it might have been tweaked or generated by a previous version of the IDE snippet).
Inheretance doesn’t work well for code re-use (conflates type hierarchies with code re-use, fragility of base class because you don’t know how it’s used)
How can literal code transclusion be used? How does this relate to funtorial / generic programing (e.g. type syntax directed) How does this relate to full on polymorphic programming