Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
"strictFunctionTypes" compiler option leads to error
See original GitHub issueThis is a continuation from this comment from https://github.com/supermacro/neverthrow/issues/36#issuecomment-631706079
Looks like the strictFunctionTypes compiler option leads to a rather cumbersome type error which looks to have merit.
This SO thread and the official docs on the subject are great resources for explaining what strictFunctionTypes is, but I personally have not sat down to really think this through to know what the implications for neverthrow are.
Below is a demonstration where there are type errors when the strictFunctionTypes is turned on.
Code example: https://repl.it/repls/SparseSaltyPdf
Screenshot:
Issue Analytics
- State:
- Created 3 years ago
- Comments:8 (8 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Thanks for the help @paduc!
This issue will remain open even after #41 is merged because I want to grok the subtleties of this
strictFunctionTypesflag. I am not sure if the flag doesn’t apply to methods because of a limit in the compiler, or whether there’s something fundamentally different between methods and functions such that the statement “parameter positions are checked contravariantly instead of bivariantly.” (from here) doesn’t apply to methods (which it seems to me that it should).Update:
2.3.2has been released which includes @paduc’s patch:https://github.com/supermacro/neverthrow/pull/41