Repository navigation
Make bridge generation cacheable and incremental - #33
Merged
Merged
Conversation
Map each source file to a cached prescan and IR fragment, re-parsing only files whose content changed or whose looked-up symbols now resolve differently. Skip codegen when the merged API is unchanged, rewrite only changed outputs and delete stale ones. Merge sources in a deterministic order and mark the task @CacheableTask.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
generateKneNativeBridgesis now a@CacheableTask; sources are merged in a deterministic order (roots in declaration order, files sorted by relative path) so outputs are reproducible and relocatable.build/kne/incremental, Gradle local state). A file is re-parsed only if its content changed or a symbol it looked up now resolves differently. The PSI environment is not started when nothing needs parsing.jvmResourcesmetadata was never cleaned).SymbolTable/TypeResolverwith lookup tracking;KneTypesingletons aredata objects withreadResolveso they round-trip through the cache.Note: calculator's
kne_bridges.kt/ GraalVM JSON are reordered once due to the deterministic merge order (same content); systeminfo and benchmark outputs are byte-identical.Test plan
PsiSourceParserIncrementalTest,GeneratedOutputsTest):examples:calculator:jvmTestand:examples:systeminfo:jvmTestpass; benchmark compiles--build-cacherestores themFROM-CACHE