Mark CompilerOptions as noCopy #1106
Merged
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.
I'd like to be able to cache stuff on
CompilerOptions(e.g., source affecting options, maybe even the more complicatedGetmethods), however that will requiresync.Mutex,sync.Once, etc. In order for that all to work, we must never copyCompilerOptionsby value.Adding any of those
syncstructs toCompilerOptionswill makego veterror out (correctly) for the copies. But, it's clearer to preemptively fix all of those problems now so that later PRs don't have to do it.A new
Clonemethod makes a shallow copy ofCompilerOptions; it's not "fast", but it's only used in testing. All other copies ofCompilerOptionswere simple to fix.Another restriction with caching stuff on
CompilerOptionsis thatCompilerOptionsis treated as immutable, never changing after creation. Thankfully we do that already, but it's hard to check that sort of thing statically.