7772c16033
After this commit, in the type checker, when checking convertability, we first compute a normal form without expanding opaque terms. If the terms are convertible, then we are done, and saved a lot of time by not expanding unnecessary definitions. If they are not, instead of throwing an error, we try again expanding the opaque terms. This seems to be the best of both worlds. The opaque flag is a hint for the type checker, but it would never prevent us from type checking a valid term. Signed-off-by: Leonardo de Moura <leonardo@microsoft.com>
13 lines
351 B
Lua
13 lines
351 B
Lua
local env = environment()
|
|
assert(env:is_opaque("and"))
|
|
assert(env:is_opaque("or"))
|
|
assert(env:is_opaque({"Int", "lt"}))
|
|
parse_lean_cmds([[
|
|
Definition a : Bool := true
|
|
]], env)
|
|
assert(not env:is_opaque("a"))
|
|
env:set_opaque("a", true)
|
|
assert(env:is_opaque("a"))
|
|
env:set_opaque("a", false)
|
|
assert(not env:is_opaque("a"))
|
|
assert(not env:is_opaque("b"))
|