Skip to content
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

Potential FSC issue with .NET 4.7.2 #5964

Closed
psantoro opened this issue Nov 29, 2018 · 1 comment
Closed

Potential FSC issue with .NET 4.7.2 #5964

psantoro opened this issue Nov 29, 2018 · 1 comment

Comments

@psantoro
Copy link

I'm using .NET 4.7.2 and Visual Studio 2017 Developer Command Prompt v15.9.2. When I use FSI and enter the following, it appears to work fine:

let hset = System.Collections.Generic.HashSet(100, HashIdentity.Structural);;

However, if I try to compile a file with using the same .NET 4.7.2 HashSet constructor via FSC, I get compile errors similar to the following:

hashset.fs(11,60): error FS0001: The type 'int' is not compatible with the type 'IEnumerable'

hashset.fs(11,60): error FS0193: Type constraint mismatch. The type
'int'
is not compatible with type
'IEnumerable'

Repro steps

Provide the steps required to reproduce the problem

  1. Open Visual Studio 2017 Developer Command Prompt v15.9.2 on system with .NET 4.7.2 installed.

  2. Use FSC to compile file using the new .NET 4.7.2 HashSet constructor noted above (see attached sample file).

If possible attach a zip file with the repro case. This often makes it easier for others to reproduce.
The zip file should ideally represent the situation just before the call/step that is problematic.

Expected behavior

I expect the F# command line tools to support the latest installed .NET version.

Actual behavior

It appears that .NET 4.7.2 is not supported by FSC. I'm guessing this is related to issue #4946.

Known workarounds

None.

Provide a description of any known workarounds.

Related information

Provide any related information

@cartermp
Copy link
Contributor

cartermp commented Dec 1, 2018

Yes, this is ultimately caused by #4946. I'll close as a duplicate of that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants