lean2/tests/lean/lua5.lean

Import Int.
Variable x : Int

(**
local N   = 100
local env = get_environment()
-- Create N variables with the same type of x
typeofx = env:type_check(Const("x"))
for i = 1, N do
    env:add_var("y_" .. i, typeofx)
end
**)

Show Environment 101
Check x + y_1 + y_2
chore(builtin): rename nat, int and real modules to Nat, Int and Real. Signed-off-by: Leonardo de Moura <leonardo@microsoft.com> 2014-01-01 21:52:25 +00:00			`Import Int.`
feat(lua): allow lua scripts (embedded in Lean files) to access the environment Signed-off-by: Leonardo de Moura <leonardo@microsoft.com> 2013-11-10 18:12:43 +00:00			`Variable x : Int`

feat(lua): use ( ... ) instead of {{ ... }} for nested Lua scripts The token }} is a bad delimiter for blocks of Lua script code nested in Lean files. The problem is that the sequence }} occurs very often in Lua code because Lua uses { and } to build tables/lists/arrays. Here is an example of Lua code that contains the sequence }} t = {{1, 2}, {2, 3}, {3, 4}} In Lean, (* ... ) is used to create comments. Thus, (* ... **) code blocks will not affect valid Lean files. It also looks reasonably good. Signed-off-by: Leonardo de Moura <leonardo@microsoft.com> 2013-11-13 00:05:46 +00:00			`(**`
chore(lua): rename env() to get_env() Signed-off-by: Leonardo de Moura <leonardo@microsoft.com> 2013-11-13 21:58:51 +00:00			`local N = 100`
			`local env = get_environment()`
feat(lua): allow lua scripts (embedded in Lean files) to access the environment Signed-off-by: Leonardo de Moura <leonardo@microsoft.com> 2013-11-10 18:12:43 +00:00			`-- Create N variables with the same type of x`
refactor(kernel/type_checker): combine type_checker and type_inferer into a single class, and avoid code duplication Signed-off-by: Leonardo de Moura <leonardo@microsoft.com> 2013-12-22 19:51:38 +00:00			`typeofx = env:type_check(Const("x"))`
feat(lua): allow lua scripts (embedded in Lean files) to access the environment Signed-off-by: Leonardo de Moura <leonardo@microsoft.com> 2013-11-10 18:12:43 +00:00			`for i = 1, N do`
chore(lua): rename env() to get_env() Signed-off-by: Leonardo de Moura <leonardo@microsoft.com> 2013-11-13 21:58:51 +00:00			`env:add_var("y_" .. i, typeofx)`
feat(lua): allow lua scripts (embedded in Lean files) to access the environment Signed-off-by: Leonardo de Moura <leonardo@microsoft.com> 2013-11-10 18:12:43 +00:00			`end`
feat(lua): use ( ... ) instead of {{ ... }} for nested Lua scripts The token }} is a bad delimiter for blocks of Lua script code nested in Lean files. The problem is that the sequence }} occurs very often in Lua code because Lua uses { and } to build tables/lists/arrays. Here is an example of Lua code that contains the sequence }} t = {{1, 2}, {2, 3}, {3, 4}} In Lean, (* ... ) is used to create comments. Thus, (* ... **) code blocks will not affect valid Lean files. It also looks reasonably good. Signed-off-by: Leonardo de Moura <leonardo@microsoft.com> 2013-11-13 00:05:46 +00:00			`**)`
feat(lua): allow lua scripts (embedded in Lean files) to access the environment Signed-off-by: Leonardo de Moura <leonardo@microsoft.com> 2013-11-10 18:12:43 +00:00
			`Show Environment 101`
			`Check x + y_1 + y_2`