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

Basic out of order compilation #264

Open
stevehalliwell opened this issue Jul 12, 2024 · 0 comments
Open

Basic out of order compilation #264

stevehalliwell opened this issue Jul 12, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@stevehalliwell
Copy link
Owner

Presently the compiler expects to be fed elements in the order they are required. As projects get larger this becomes more of a unwanted burden.

A starting improvement here might to be compile a chunk at a time, if a chunk fails to compile due to external name not found. It aborts the chunk, orders itself at the bottom of the compile queue and compilation continues. We could detect compile stall outs by tracking the last reported error from the items in the compile queue, if a full iteration of it results in exactly the same errors in each we are stalled.

Another option would be to look back at c and introduce forward declare concept, a trust me, this thing will exist. In cases where that would be a direct bind to a chunk/closure that's just going to require a later patch up.

@stevehalliwell stevehalliwell added the enhancement New feature or request label Jul 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant