Keean Schupke

So then when we have: ``` f(x) => x.call_widget() ``` We can clearly see no code in `f` is inserting any implementations into anything. Sorry to have to take it...

> For macros we only need #​1 - 3 I don't want macros :-) I don't want a second weaker version of application in a language. What you are basically...

Macro's are bad and are included in languages because normal function application is not powerful enough. If you want a function write a function.

Macro's provide an escape hatch to bypass the type system (in some languages), this is a bad thing. Messing about with the program code itself using macro splicing is a...

Macros also make debugging harder as they are applied at compile time. Any errors reported at runtime will be in the post macro processed code, so the line numbers and...

Maybe you can persuade me, if you can provide an example of a macro that cannot be more cleanly implemented in another way?

> Macros enable editing the source code of the arguments before they are evaluated. I know what macro's are, I am saying there is always a better way to do...

I have not written a macro for about 20 years, so that someday was decades ago :-)

You do not need macro's to create DSLs. > Show me how to write a SQL query DSL Sure I did it in Haskell back in 2004 :-)

What's obtuse about this: ```haskell moveContaminatedAnimal :: DAnimalType -> DCntdType -> DFarmId -> Query () moveContaminatedAnimal animalType contaminationType newLocation = do a1