Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upType mismatch for tuple union types passed to tuple functions #827
Comments
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
process-bot
Jan 29, 2017
Thanks for the issue! Make sure it satisfies this checklist. My human colleagues will appreciate it!
Here is what to expect next, and if anyone wants to comment, keep these things in mind.
process-bot
commented
Jan 29, 2017
|
Thanks for the issue! Make sure it satisfies this checklist. My human colleagues will appreciate it! Here is what to expect next, and if anyone wants to comment, keep these things in mind. |
zeddidragon
changed the title from
Type mismatch for tuple union types
to
Type mismatch for tuple union types passed to tuple functions
Jan 29, 2017
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
mgold
Jan 30, 2017
Contributor
This behaves as designed and is unlikely to be changed. I can go into more depth if you ask on the mailing list.
|
This behaves as designed and is unlikely to be changed. I can go into more depth if you ask on the mailing list. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
|
Max is right. I'm closing this issue. |
zeddidragon commentedJan 29, 2017
•
edited
Edited 1 time
-
zeddidragon
edited Jan 29, 2017 (most recent)
Steps to reproduce:
Actual result:
Expected result:
Program compiles, herp is 1
Since any instance of Foo is guaranteed to be a tuple where the second element is an Int, it should be reasonable to expect a function that only cares about the second element of the tuple to accept instances of Foo.
Version
Elm version 0.18.0 for OSX