[RFC007] Migration of the typechecker part II - focus on bytecode::ast::typecheck
#2170
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Sorry about the name, it is not very inspired. This PR is a split of the behemoth of #2134 that has become unmanageable, leading to unexpected and mandatory changes to many parts of Nickel. The current PR only keeps the changes to
bytecode::ast
, and doesn't actually get rid of the old typechecker, but instead only modifiesbytecode::ast::typecheck
.The changes that landed here comes from actually testing the new typechecker, making all the tests of
nickel-lang-core
pass. It also includes various helpers additions to thebytecode::ast
module.