Fsharp: typecheck error FS0192: error : tcrefOfAppTy

[haraldsteinlechner]

We found a combination of extensions and overloads which breaks the compiler.

@krauthaufen @aszabo314

Repro steps

clone the repo: https://github.com/haraldsteinlechner/badCop
and build...

Expected behavior

prints compile errors

Actual behavior

fails internally with:

2>typecheck error FS0192: error : tcrefOfAppTy
2>typecheck error FS0073: error : tcrefOfAppTy (Failure)
2>parameter error FS0192: error : tcrefOfAppTy
2>  Unhandled Exception: System.Exception: tcrefOfAppT

Known workarounds

not having compile erros. In our setting we have no workaround yet, since we use compilerservice to parse and check projects with errors.

Related information

newest fsharp compiler and compiler services

[forki]

interesting. this only happens in VS. it doesn't in ionide

[haraldsteinlechner]

well, the problem occurs in pretty printing of potential overloads. is it possible to disable those precise error messages? @forki

[forki]

ok I can repro inside the fsc.exe

[haraldsteinlechner]

the problem occurs:

• in ionide when using netcore etc
• in vanilla msbuild
• dotnet build
• in compiler services
• in fsc

we now have a dotnet branch of the repro repo: https://github.com/haraldsteinlechner/badCop/tree/netcore

[forki]

found a possible fix:

[forki]

lol that comment abot the formatter

/// Format a method info using "half C# style".

[forki]

fix is in https://github.com/Microsoft/visualfsharp/pull/4826

[haraldsteinlechner]

nice one!

[haraldsteinlechner]

what is the policy regarding duplicate fixes in compiler service?

[forki]

What do you mean?

Harald Steinlechner [e-mail] schrieb am Fr., 4. Mai 2018,
12:46:

what is the policy regarding duplicate fixes in compiler service?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/visualfsharp/issues/4825#issuecomment-386565202,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AADgNOph_imEWd3dbEtcHjLqvE7pOBBKks5tvDF-gaJpZM4TyTKh
.

[haraldsteinlechner]

the same problem occurs in f# compiler services (that is the second spot we stumbled across this issue)

[forki]

FCS is part of this repo and the fix applies there as well. After it is
merged @dsyme will push the nuget eventually. In other words: nothing is
needed to do for fcs here

Harald Steinlechner [e-mail] schrieb am Fr., 4. Mai 2018,
12:51:

the same problem occurs in f# compiler services (that is the second spot
we stumbled across this issue)

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/visualfsharp/issues/4825#issuecomment-386566164,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AADgNAiyUhptgtdL-8fRRynVg68guMfHks5tvDKYgaJpZM4TyTKh
.

[haraldsteinlechner]

awesome, thanks

[KevinRansom]

Re-opening per @forki

[abelbraaksma]

This was marked "ready", was it solved? Can it be closed?

[krauthaufen]

At least on our end the issue didn't occur for a while...
Correct me if I'm wrong @haraldsteinlechner

[haraldsteinlechner]

nope never happened and original repo seems to be "solved" as well.

[abelbraaksma]

@haraldsteinlechner, sorry, I don't get it. Do you mean "never happened: the issue disappeared and didn't come back after the fix" or "never happened: a fix was never implemented/working or seen"?

If it is fixed, you can close this issue.

[haraldsteinlechner]

should have been never happened again ;)