teach F# 4.0 compiler about future 4.1+ native intrinsics #16
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.
In short, I recommend we incorporate this otherwise-harmless change to F# 4.0.
In this comment thread, we are quite concerned about the impact of the F# 4.0 library using new F# library metadata formats that would cause a failure-on-startup if FSharp.Core 4.4.0.0 is fed to an F# 3.1 compiler, regardless of whether the new NativePtr functions are actually used by user code or not.
It is getting harder to do much about F# 3.1 compiler behaviour, but we can at least make sure that the F# 4.0 compiler doesn't suffer the same problem. We can minimally do this by adding the necessary contstructs to the metadata format reader inn the F# 4.0 compiler. These should reeally have been present from the start in all editions of the F# compiler anyway.