You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The error message points at the unwrap() call at core/src/repl/mod.rs:116:64. This panic doesn't happen when trying to evaluate foo.ncl from the CLI, or in fact when trying another file that imports foo.ncl.
The text was updated successfully, but these errors were encountered:
* Add a Types variant to Term
* Mark Types as non-atomic
* Update core/src/term/mod.rs
Co-authored-by: Yann Hamdaoui <yann.hamdaoui@tweag.io>
* Only allow without_pos in tests
* Review comments
* Add a comment
* Improve typechecking of types in contract position
* Add a test for the new error
* Update core/src/eval/mod.rs
Co-authored-by: Yann Hamdaoui <yann.hamdaoui@tweag.io>
* Improve comment
---------
Co-authored-by: Yann Hamdaoui <yann.hamdaoui@tweag.io>
With two files like so:
that is,
foo.ncl
immediately importsbar.ncl
andbar.ncl
contains a parse error, the REPL panics on importingfoo.ncl
:The error message points at the
unwrap()
call atcore/src/repl/mod.rs:116:64
. This panic doesn't happen when trying to evaluatefoo.ncl
from the CLI, or in fact when trying another file that importsfoo.ncl
.The text was updated successfully, but these errors were encountered: