-
Notifications
You must be signed in to change notification settings - Fork 138
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Empty data types depending on type literals don't behave as expected #2447
Comments
Hey, for the error I will have to take a deeper look to fix it (the literal The, it is this Like in #2457 LH can relate the type variable with the value parameter only by the information you specify in the data constructor signature. So, the following has some behavior close to the one I expect you want it to have
|
Interesting observation. I wasn't aware of that and no, I don't have any knowledge of how
No, I don't like to error in the term literal Your modification also does not LH type check for me. It complains about the declaration of
|
I wanna make use of some dependently uninhabited data types, where the following references the expected behavior
However, if I parameterize the above with a type natural, then false detection stops working in the uninhabited case
It also gives me a
for
getSomeZeroT
unless I enable--prune-unsorted
, which might be related, I guess.2024-12-17: Update of the reproducer to work with 791567f.
The text was updated successfully, but these errors were encountered: