Test/Transparent Compiler: test that TC reuses check results after project modifications - #20444
Open
DedSec256 wants to merge 1 commit into
Open
Test/Transparent Compiler: test that TC reuses check results after project modifications#20444DedSec256 wants to merge 1 commit into
DedSec256 wants to merge 1 commit into
Conversation
…oject modifications
Contributor
✅ No release notes required |
github-actions
Bot
added
the
AI-Tooling-Check-Scanned-Clean
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
1 participant
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.
Description
Adds tests for #16823 that pin down how the Transparent Compiler reuses cached type-check results when the structure of a project changes: a file is added or moved.
One behaviour worth flagging
Adding a file at the end of the project checks everything when the assembly name is implicitis marked with a//TODO:--out:in the options,TcConfigBuilder.DecideNamesderives the assembly name from the last implementation file.BootstrapInfoStaticcache, which is keyed onBaseCacheKeyWith("BootstrapInfoStatic", assemblyName).BootstrapInfo.Id, which is mixed into everyTcIntermediatekey viaWithExtraVersion.The paired
--out:test isolates this: pin the assembly name and the same edit costs one file.