Further improve compilation performance and reduce compiled module size #132
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.
Fixes #110
problem_tuple
types. One approach might be to compile all module atom names, so we still have a stricter way to disambugate particular problem_tuples in the formatter and for data generation?The example code of the example now results in an Erlang core module of only ~138MB large, and compiles in roughly 15s on my local computer. (On faster computers, it probably will be sub-10s). I think this is as far as we can push this, without moving away from compiling all checks inline (which is out of scope for now, although it makes sense to add this in a future version.)