New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Implement separate file compilation in Sparrow #32

Open

lucteo opened this issue Jan 22, 2017 · 0 comments

Contributor

lucteo commented Jan 22, 2017

For larger projects, we may have multiple sparrow source files that we would like to compile individually.

Main ideas:

non-generic functions are only compiled (e.g., code generation) for the translation unit in which they appear
each function (and class) should have an unique name, so that we can properly find the symbols at link time
the same generic can be generated into multiple files, but at link time, they should all collapse to only one

Make sure this works at least with the Sparrow parser code.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment