Inconsistent type incompatible error range
See original GitHub issuelet f (i: System.IDisposable) = ()
let o = obj()
o |> f
f o
The highlighted range is different between cases when using a prefix application and a pipe operator: in one case the argument is highlighted and in another cases it’s the function:
Maybe it’d be better (and feasible?) to highlight the same thing in both cases?
Issue Analytics
- State:
- Created a year ago
- Reactions:1
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Inconsistent "possible lossy conversion from int to byte" ...
In case 1, the operands are of type int, so the overall expression is of type int, so it is incompatible. In case...
Read more >Excel Tips: A Trick for Finding Inconsistent Data
Finding inconsistent data in a large spreadsheet can be time consuming. This Excel trick can make it much easier.
Read more >My Experience in dealing with inconsistent number range ...
I am sharing my experience in dealing with many inconsistent issues, number range issues, express document/update fails. Sometimes user may ...
Read more >Fix an inconsistent formula
Troubleshoot why it's inconsistent. Click Formulas > Show Formulas. Doing that lets you see the formulas in all cells, instead of the calculated...
Read more >Identify Inconsistent and Incomplete Formal Requirement ...
When using a Requirements Table block, you can identify inconsistent and incomplete requirement sets, and find read-before-write errors.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@charlesroddie The error is the same in both cases and is specifically about
obj
argument type being incompatible withIDisposable
, so it’d probably be nice to highlight the argument.This is not a bug - I agree with @charlesroddie’s analysis here