You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It will allow us to have the compiler avoid doing work it's already done on subsequent runs of check and build.
Instead of parsing and type checking modules that won't often change from dependencies we can load up the fully type checked module from the file system.
What is the current alternative and why is it not good enough?
The current state is such that the compiler must parse and type check every module on every invocation of the compiler. In the future as projects grow this should help reduce the time it takes to compile entire projects.
toolingTooling and developer experience improvements
1 participant
Converted from issue
This discussion was converted from issue #861 on May 09, 2024 12:17.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
What is your idea? Provide a use case.
Cache dependencies using
CheckedModule::to_cbor
.Why is it a good idea?
It will allow us to have the compiler avoid doing work it's already done on subsequent runs of
check
andbuild
.Instead of parsing and type checking modules that won't often change from dependencies we can load up the fully type checked module from the file system.
What is the current alternative and why is it not good enough?
The current state is such that the compiler must parse and type check every module on every invocation of the compiler. In the future as projects grow this should help reduce the time it takes to compile entire projects.
Beta Was this translation helpful? Give feedback.
All reactions