Ports have an operator and optionally a timeline, but there is no way to specify which kinds of messages they send or are expecting to receive. If that were specified, then we could check that conduits connect compatible ports.
There are some potential issues with this:
- Ports may be syntactically compatible (they send and receive a float) but semantically incompatible (they send a density and expect a flux)
- MUSCLE3 allows complex messages that consist of nested dicts and lists, for which you'd need a schema language to describe them, and that could get wordy
We'll probably also want Any and Void/Nil/None types to disable type checking for a particular port (generic time bridge?) or to specify ports that send or expect to receive only empty messages.
Ports have an operator and optionally a timeline, but there is no way to specify which kinds of messages they send or are expecting to receive. If that were specified, then we could check that conduits connect compatible ports.
There are some potential issues with this:
We'll probably also want Any and Void/Nil/None types to disable type checking for a particular port (generic time bridge?) or to specify ports that send or expect to receive only empty messages.