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 upMapping over task sent out of port causes runtime error #368
Comments
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
theor
Dec 26, 2015
same problem here - a nicer error message at runtime, or even better, at compilation time would be better.
theor
commented
Dec 26, 2015
|
same problem here - a nicer error message at runtime, or even better, at compilation time would be better. |
evancz
closed this
May 11, 2016
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
mgold commentedAug 24, 2015
This program
crashes with the message
The problem appears if you (1) have a task sent out a port (2) which is mapped over by another task (3) which is itself sent out a port. If you remove the
portkeyword from either definition (on both lines), the error disappears.The workaround is to only send the final task out a port, and this makes a lot of sense. It would be fairly easy to put a better runtime error into place. However, it's not obvious how to catch this at compile time.