Neil Mitchell
Neil Mitchell
The problem with rechecking it as an annotation is that many that require Usage bindings which we only generate for things we have a suspicion are types. This one will...
I found another internal example with this problem. I've sent you the details. Happy to patch if we consider it rare and bad practice.
You can write your own UnpackValue by hand, which shouldn't be too difficult. I do agree that a reasonable UnpackValue implementation for a struct would be to UnpackValue all the...
I don't have any great ideas here - it seems a really hard problem. The definition is miles away and in a very different format. As such it seems like...
The LSP was written after the type checker, so there isn't any type information used in the LSP. We should definitely fix that one day.
You will need to use a RefCell for all operations. Assuming you also want to use this for frozen values (e.g. non-mutable), you'll have to have both a frozen version...
We don't currently have any plans to refine the type system to follow the latest Python type specification.
Using the new Hoogle at http://hoogle.haskell.org/?hoogle=%3A%3A%20(a-%3Eb)%20-%3E%20(c%2Ca)%20-%3E%20(c%2Cb) this shows up as "No query", which is definitely wrong.