Replies: 1 comment
-
Hmm yeah, this does look like a bug. And yeah, you're right, it'll take some investigation to figure out if it's FsAutocomplete or FSharp.Compiler.Service. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm asking this here as I'm not sure where to open an issue and the issue templates are quite hefty. Other issues I've opened were premature and maybe a distraction to contributors, since they may have been issues in the underlying fsharp compiler libraries powering fsautocomplete. (It's also tricky to search for an existing issue across many repos, as this may be fixed already on head).
I've found that the type hint shown for certain types where a type is parameterized by a tuple and a function are not correctly printed with the correct precedence. For example, In the screenshot below, it shows a tupled function to 'c instead of a tuple of a value and a function from unit to `c.
This affects the
Add explicit type annotation
code action, which is where I usually notice it, since the provided type causes a compilation error in otherwise working unannotated code.(In passing, another issue with the
Add explicit type annotation
I noticed is that it doesn't add therequires
bounds, so the type ends up being just `c in this specific case when it's used on an untyped token, which is valid, but perhaps surprising given that the tooling shows a more specific type.)Beta Was this translation helpful? Give feedback.
All reactions