You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The suggestion to be discussed here is the following.
Explicitly forwarding is a burden, we have to introduce twice as many names and then connect them. Combined with the current shortcoming of the lack of inference for forwarders we have to carefully pick the session and the correct order.
Consider the following function composing two processes of matching types:
Here I've marked the channels to be connected with ~ as I'm concerned of the unintended use of this feature. Still we can consider the fully implicit version.
We don't have patterns inside allocated channels but this would help even further:
The suggestion to be discussed here is the following.
Explicitly forwarding is a burden, we have to introduce twice as many names and then connect them. Combined with the current shortcoming of the lack of inference for forwarders we have to carefully pick the session and the correct order.
Consider the following function composing two processes of matching types:
I'm suggesting something along the lines of:
Here I've marked the channels to be connected with
~
as I'm concerned of the unintended use of this feature. Still we can consider the fully implicit version.We don't have patterns inside allocated channels but this would help even further:
It remains that we need to implement some basic inference first.
Any comments?
The text was updated successfully, but these errors were encountered: