>=1.3.0 causes nonsensical Intellisense/compilation errors (due to applicatives?)
See original GitHub issueAfter upgrading from 1.2.6 to 1.3.0 or above, I get nonsensical compilation errors:

I guess this has to do with applicatives.
I am using <LangVersion>preview</LangVersion> to get access to nameof, which I use extensively in logging.
It builds fine with the VSBuild task on Azure Pipelines, but locally there’s nothing that can make it compile except downgrading to 1.2.6.
Note that I am not even using and!; the error come just from upgrading FsToolkit.ErrorHandling.
The errors can often be “fixed” by reordering the bang operator lines if possible, but that’s not always possible nor desirable. For example like the below (which can’t be used due to incorrect behavior):

Issue Analytics
- State:
- Created 3 years ago
- Comments:9 (2 by maintainers)
Top Results From Across the Web
No results found
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 Free
Top 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

Thanks for the tip. I’ll stick with 1.2.6 for now; it’s the most non-intrusive solution.
Was fixed in an updated VS version, to be specific. Don’t remember exactly which. The referenced FSharp.Core version seems irrelevant.