[REG 2.095] Fix build regression when compiling dmd using separate compilation #11827
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.
dmd.root.stringtable.StringValue!(Type)
andcore.internal.array.equality.__equals!(Ensure[], Ensure[])
when building the dmd front-end using separate compilation method. Closes Issue 21294, however the underlying cause of templates not being emitted is being worked on by @atilaneves and co.dmd.root.stringtable.StringValue!(Type)
when the host compiler is dmd.When compiling dmd modules separately, there is still undefined references to the symbol
dmd.root.stringtable.StringTable!(Symbol)
, this can be resolved by adding the following leaf module should it ever become a probem: