Don Syme

I've linked this in https://github.com/dotnet/fsharp/pull/6805 to investigate this in the context of that branch work

Regarding priority - please note that FSharpPlus is using a combination of techniques (SRTP, overloading of witnesses, chained-generation of new SRTP constraints during solving, subtyping etc.) that are not appropriate...

Note I haven't fully validated that it's the F# compiler causing the incorrect instantiation, the above is based on reviewing the relevant code in FSHarp.Data and concluding that it must...

Notes using dotnet/fsharp main 1. Script editing, Project editing, Project compilation These seems to set ResolutionFolder correctly 3. Interactive execution e.g. `artifacts\bin\fsi\Debug\net472\fsi.exe c:\misc\a.fsx` This is setting ResolutionFolder to `C:\\Users\\Administrator\\AppData\\Local\\Temp\\nuget\\27164--ec6048ac-4d32-4dec-bdda-205b40cc3455"` -...

OK, I can see a fix to propose @KevinRansom I'll catch you on teams

We always intended to do this, but the reliance on a choice type encoding held us back, plus the general complexity compared to number of use cases. The metadata allows...

I guess that qualifies as an approve in principle

This needs a language design suggestion - but please consider it pre-approved. It is a missing case that has come up before but which would be really good to complete.

> Do you mean a RFC in the fslang-design repo @dsyme? That's the next step. I mistakenly thought I was replying to dotnet/fsharp issue

@KathleenDollard and I started looking at systematically improving mismatches in argument application Here is the start of a matrix and "ideal" error messages that begin to follow a system. WIP....