-
Notifications
You must be signed in to change notification settings - Fork 789
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow F# assemblies to run in .NET Native #593
Comments
In addition to looking for a technical workaround for this issue, everyone who's interested in running F# on .NET Native should make sure to vote up these UserVoice issues to make their interest known to Microsoft:
@ovatsus I suspect you've already seen these, I just figured I'd post them here to remind anyone who finds this issue and hasn't voted. |
I have potentially made. Net native more difficult with #513 (currently in limbo, but I think it is going to be sucked into the main code base). Basically the change does for comparison identity.structural and hashIdentity.Structural what comparer.default/equalitycomparer.default do i.e. make efficient comparison interfaces but using the more complex f#rules of equality. This also affects relationship operators and equality. Now late in the day .net native was mentioned and I have a couple of ideas how to proceed:
Anyway just polling if any of these are palatable, or if you have any other ideas? |
Duplicate of #1096 |
I guess this is probably not the right place to put this, but as there was an item for supporting CoreCLR already, I think this one also makes sense.
Is there anything that could be done in the compiler to fool the .NET Native compiler to be able to handle F# assemblies, by avoiding the use of specific constructs?
The text was updated successfully, but these errors were encountered: