Set lambda linkage to LinkOnceODR (was Internal) #5045
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.
This reverts #4415. The mangling of lambdas has been fixed (and is now stable and cannot clash with other modules anymore), so there is no longer a need for internal linkage. This allows merging of identical lambdas again (multiple instantiations).
This also fixes an instantiation bug, where the lambda's emission is sometimes culled because the frontend knows it is already instantiated in another module, but because of internal linkage it cannot resolve the symbol during linking (thus resulting in a missing symbol during linking).