Include AST info in serialized module files #52
Comments
|
...walking around this with silly hacks is proving to be more and more expensive as I proceed, so at this point I'll probably just fold this into #50. |
griwes
added a commit
to griwes/vapor
that referenced
this issue
May 3, 2019
One big missing thing is importing default implementations of typeclass member functions, but that will come at a later date when I figure out how the heck to serialize function definitions. This is the first commit that touches in reaver-project#52; it is by no means a proper implementation of that, since it mostly only _reads_ the AST location info from the module files; it doesn't really _write_ them, which is something that will require a more proper pass over everything we export. This also somewhat improves dependencies for proto files; it's slightly overeager there, because all proto files are re-compiled when any of them changes. To make testcases more interesting, integer division has been implemented.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, the module files don't contain any AST info; this is bad, since it makes good error messages essentially impossible. It also makes a few places in code awkward, like, for instance, it makes it necessary to have two constructors in
typeclass_expression, which is what I'd like to fix as I'm adding it, but it seems like a bigger effort than what I want to include in typeclasses themselves.(Nevermind that I've already done some big changes not related to the feature on that branch. Everything is fine.)
The text was updated successfully, but these errors were encountered: