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 6 Chapter 3. Language Reference Agda Documentation, Release 2.5.2 module 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 6 Chapter 3. Language Reference Agda Documentation, Release 2.5.3 module 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 (continues on next page) 10 Chapter 3. Language Reference Agda User Manual 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] 3.18.8 Splitting a program over multiple files When building large programs it is crucial to be able to split the program over multiple

checking an abstract definition, the abstract definitions of the parent module are transparent: module M1 where abstract x = 0 (continues on next page) 10 Chapter 3. Language Reference Agda User Manual 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] 3.18.8 Splitting a program over multiple files When building large programs it is crucial to be able to split the program over multiple

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 (continues on next page) 10 Chapter 3. Language Reference Agda User Manual 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] 3.18.8 Splitting a program over multiple files When building large programs it is crucial to be able to split the program over multiple

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