Skip to content
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.

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

Savable bytecode #10

Open
alekratz opened this issue Jul 24, 2017 · 0 comments
Open

Savable bytecode #10

alekratz opened this issue Jul 24, 2017 · 0 comments

Comments

@alekratz
Copy link
Owner

This would be a nice feature to have, since every time we pull in files they get parsed/compiled, which becomes redundant if you're just updating one file at a time.

Caveats/considerations:

  • Do we store debug/file symbol and information? (e.g. source path + location where each bytecode instruction gets generated from) Will we support stripping of this information?
  • Compiled file names and detecting when to re-compile and import *.sblc (or whatever the extension is)
    • Imports are done by direct path, which needs to be taken into consideration.
  • General file format
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant