Idris2/tests/idris2/reflection002/expected

1/1: Building power (power.idr)
Main> Main.cube : Nat -> Nat
cube = \x => mult x (mult x (mult x (const (fromInteger 1) x)))
Main> 27
Main> Main.cube' : Nat -> Nat
cube' = \x => mult (mult (mult (const (fromInteger 1) x) x) x) x
Main> 27
Main> Bye for now!
Progress on elaborator reflection Add %runElab and start on scripts, although all they can do so far is check a term. This does gives us, sort of, "template Idris" (as demonstrated in test reflection002) 2020-05-31 03:36:54 +03:00			`1/1: Building power (power.idr)`
			`Main> Main.cube : Nat -> Nat`
Reduce amount of normalisation in elab scripts We don't want to unfold definitions in 'pure' or 'check' or 'bind' since we want the exact expression that the script author has used. 2020-06-03 02:22:03 +03:00			`cube = \x => mult x (mult x (mult x (const (fromInteger 1) x)))`
Progress on elaborator reflection Add %runElab and start on scripts, although all they can do so far is check a term. This does gives us, sort of, "template Idris" (as demonstrated in test reflection002) 2020-05-31 03:36:54 +03:00			`Main> 27`
Add alternative example to reflection002 A bit more typesafe... 2020-06-03 01:56:30 +03:00			`Main> Main.cube' : Nat -> Nat`
Reduce amount of normalisation in elab scripts We don't want to unfold definitions in 'pure' or 'check' or 'bind' since we want the exact expression that the script author has used. 2020-06-03 02:22:03 +03:00			`cube' = \x => mult (mult (mult (const (fromInteger 1) x) x) x) x`
Add alternative example to reflection002 A bit more typesafe... 2020-06-03 01:56:30 +03:00			`Main> 27`
Progress on elaborator reflection Add %runElab and start on scripts, although all they can do so far is check a term. This does gives us, sort of, "template Idris" (as demonstrated in test reflection002) 2020-05-31 03:36:54 +03:00			`Main> Bye for now!`