only an echo statement in its body: import std/macros macro m1(s: string): untyped = echo s proc main = echo "calling macro m1" m1("Macro argument") main() When we compile the above code, the the macro body. When we run the program, we get only the output "calling macro m1" from the main() proc, as the macro m1() does only return an empty AST. The careful reader may wonder why the echo() echo() statement in the macro body above works at all, since the parameter of macro m1() is specified as an ordinary string, not as a static[string]. So the type of s in the macro body should be a NimNode

only an echo statement in its body: import std/macros macro m1(s: string): untyped = echo s proc main = echo "calling macro m1" m1("Macro argument") main() When we compile the above code, the the macro body. When we run the program, we get only the output "calling macro m1" from the main() proc, as the macro m1() does only return an empty AST. The careful reader may wonder why the echo() echo() statement in the macro body above works at all, since the parameter of macro m1() is specified as an ordinary string, not as a static[string]. So the type of s in the macro body should be a NimNode

checking an abstract definition, the abstract definitions of the parent module are transparent: module M1 where abstract x = 0 module M2 where abstract x-is-0 : x ≡ 0 x-is-0 = refl Thus is module M1 Δ = M2 terms modifiers A common pattern is to apply a module to its arguments and then open the resulting module. To simplify this we introduce the short-hand open module M1 Δ = M2 terms terms [public] mods for module M1 Δ = M2 terms mods open M1 [public] Splitting a program over multiple files When building large programs it is crucial to be able to split the program over multiple files

checking an abstract definition, the abstract definitions of the parent module are transparent: module M1 where abstract x = 0 module M2 where abstract x-is-0 : x ≡ 0 x-is-0 = refl Thus is module M1 Δ = M2 terms modifiers A common pattern is to apply a module to its arguments and then open the resulting module. To simplify this we introduce the short-hand open module M1 Δ = M2 terms terms [public] mods for module M1 Δ = M2 terms mods open M1 [public] Splitting a program over multiple files When building large programs it is crucial to be able to split the program over multiple files

checking an abstract definition, the abstract definitions of the parent module are transparent: module M1 where abstract x = 0 module M2 where abstract x-is-0 : x ≡ 0 x-is-0 = refl Thus is module M1 Δ = M2 terms modifiers A common pattern is to apply a module to its arguments and then open the resulting module. To simplify this we introduce the short-hand open module M1 Δ = M2 terms terms [public] mods for module M1 Δ = M2 terms mods open M1 [public] Splitting a program over multiple files When building large programs it is crucial to be able to split the program over multiple files

checking an abstract definition, the abstract definitions of the parent module are transparent: module M1 where abstract x = 0 module M2 where abstract x-is-0 : x ≡ 0 x-is-0 = refl Thus is module M1 Δ = M2 terms modifiers A common pattern is to apply a module to its arguments and then open the resulting module. To simplify this we introduce the short-hand open module M1 Δ = M2 terms terms [public] mods for module M1 Δ = M2 terms mods open M1 [public] Splitting a program over multiple files When building large programs it is crucial to be able to split the program over multiple files

checking an abstract definition, the abstract definitions of the parent module are transparent: module M1 where abstract x = 0 module M2 where abstract x-is-0 : x ≡ 0 x-is-0 = refl Thus is module M1 Δ = M2 terms modifiers A common pattern is to apply a module to its arguments and then open the resulting module. To simplify this we introduce the short-hand open module M1 Δ = M2 terms terms [public] mods for module M1 Δ = M2 terms mods open M1 [public] Splitting a program over multiple files When building large programs it is crucial to be able to split the program over multiple files

checking an abstract definition, the abstract definitions of the parent module are transparent: module M1 where abstract x = 0 module M2 where abstract x-is-0 : x ≡ 0 x-is-0 = refl Thus is module M1 Δ = M2 terms modifiers A common pattern is to apply a module to its arguments and then open the resulting module. To simplify this we introduce the short-hand open module M1 Δ = M2 terms terms [public] mods for module M1 Δ = M2 terms mods open M1 [public] Splitting a program over multiple files When building large programs it is crucial to be able to split the program over multiple files