3651dc7618
The implementation is good enough for implementing extensible parsers, elaborators and tactics, but there are a few TODOs 1- We should have a better story for standalone applications. Most of them don't need `evalConst`, and the global table is just initialization overhead. 2- The global table introduces a dependency on the `Lean.Name` implementation. So, all standalone applications will depend on it. 3- We are not storing arity 0 constants in the table. This one should be easy to fix in the future.
13 lines
358 B
Text
13 lines
358 B
Text
/-
|
|
Copyright (c) 2019 Microsoft Corporation. All rights reserved.
|
|
Released under Apache 2.0 license as described in the file LICENSE.
|
|
Authors: Leonardo de Moura
|
|
-/
|
|
prelude
|
|
import init.lean.compiler
|
|
import init.lean.extern
|
|
import init.lean.environment
|
|
import init.lean.modifiers
|
|
import init.lean.runtime
|
|
import init.lean.attributes
|
|
import init.lean.evalconst
|