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
Existing Range implementation has :sig inport just so we could write
:start -> 1..11 -> list -> println -> :stop
Instead of
:start -> { 1..11 -> list -> println -> :stop }
But that mean we always have to have something that will kick range. In that example that was the case so that was handy but is it worth it? Deferred connections are more universal in that regard and allow both cases - with and without separate kicker. E.g. imagine you wanna create RangeWrapper - you'll end up having all 3 inports :from, :to and :sig.
Other Syntax Forms
This problem is related to all #731 that might have kicker :sig to avoid deferred connections.
Maybe for constants having :sig inport makes sense, maybe they are really special case. As long as they are not "one-shot" things they do need something to trigger them (or defer, like now)
The text was updated successfully, but these errors were encountered:
Range Case
Existing
Range
implementation has:sig
inport just so we could writeInstead of
But that mean we always have to have something that will kick range. In that example that was the case so that was handy but is it worth it? Deferred connections are more universal in that regard and allow both cases - with and without separate kicker. E.g. imagine you wanna create
RangeWrapper
- you'll end up having all 3 inports:from
,:to
and:sig
.Other Syntax Forms
This problem is related to all #731 that might have kicker
:sig
to avoid deferred connections.Constants
Related to #717
Maybe for constants having
:sig
inport makes sense, maybe they are really special case. As long as they are not "one-shot" things they do need something to trigger them (or defer, like now)The text was updated successfully, but these errors were encountered: