lean2/tests/lean/lua6.lean

Variable x : Int
SetOption pp::notation false
(**
print(get_options())
**)
Check x + 2
(**
o = get_options()
o = o:update(name('lean', 'pp', 'notation'), true)
set_options(o)
print(get_options())
**)
Check x + 2
(**
set_option(name('lean', 'pp', 'notation'), false)
print(get_options())
**)
Variable y : Int
Check x + y
feat(lua): allow Lua scripts to update 'global' options Signed-off-by: Leonardo de Moura <leonardo@microsoft.com> 2013-11-12 15:38:00 -08:00			`Variable x : Int`
feat(frontends/lean): rename command Set to SetOption It is not nice to have Set as a reserved keyword. See example examples/lean/set.lean Signed-off-by: Leonardo de Moura <leonardo@microsoft.com> 2013-12-18 21:18:45 -08:00			`SetOption pp::notation false`
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-12 16:05:46 -08:00			`(**`
feat(lua): allow Lua scripts to update 'global' options Signed-off-by: Leonardo de Moura <leonardo@microsoft.com> 2013-11-12 15:38:00 -08:00			`print(get_options())`
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-12 16:05:46 -08:00			`**)`
feat(lua): allow Lua scripts to update 'global' options Signed-off-by: Leonardo de Moura <leonardo@microsoft.com> 2013-11-12 15:38:00 -08:00			`Check x + 2`
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-12 16:05:46 -08:00			`(**`
feat(lua): allow Lua scripts to update 'global' options Signed-off-by: Leonardo de Moura <leonardo@microsoft.com> 2013-11-12 15:38:00 -08:00			`o = get_options()`
			`o = o:update(name('lean', 'pp', 'notation'), true)`
			`set_options(o)`
			`print(get_options())`
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-12 16:05:46 -08:00			`**)`
feat(lua): allow Lua scripts to update 'global' options Signed-off-by: Leonardo de Moura <leonardo@microsoft.com> 2013-11-12 15:38:00 -08:00			`Check x + 2`
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-12 16:05:46 -08:00			`(**`
feat(lua): allow Lua scripts to update 'global' options Signed-off-by: Leonardo de Moura <leonardo@microsoft.com> 2013-11-12 15:38:00 -08:00			`set_option(name('lean', 'pp', 'notation'), false)`
			`print(get_options())`
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-12 16:05:46 -08:00			`**)`
feat(lua): allow Lua scripts to update 'global' options Signed-off-by: Leonardo de Moura <leonardo@microsoft.com> 2013-11-12 15:38:00 -08:00			`Variable y : Int`
			`Check x + y`