We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
See #721 this is an extension
(bool_sender ? res_sender1 : res_sender2) -> dst
flow Main(start) (stop) { Eq, Ternary, Println --- :start -> [(2 -> eq:actual), (2 -> eq:compared)] eq -> ternary:if 'They match' -> ternary:then 'They do not match' -> ternary:else ternary -> println -> :stop }
flow Main(start) (stop) { Eq, Println --- :start -> [(2 -> eq:actual), (2 -> eq:compared)] (eq ? 'They match' : 'They do not match') -> println -> :stop }
flow Main(start) (stop) { Eq, Println --- :start -> [2 -> eq:actual, 2 -> eq:compared] eq -> (eq ? 'They match' : 'They do not match') -> println -> :stop }
In case these chains will support trigger semantics
flow Main(start) (stop) { Println --- :start -> ((2 == 2) ? 'They match' : 'They do not match') -> println -> :stop }
The text was updated successfully, but these errors were encountered:
Plus #721
Instead of adding trigger semantics to () we can use deferred connections here (if they are existing)
()
flow Main(start) (stop) { Println --- :start -> |((2 == 2) ? 'They match' : 'They do not match') -> println -> :stop| }
Noisy AF but something to think about
Sorry, something went wrong.
#738
No branches or pull requests
See #721 this is an extension
Before
After
With #717
Plus #721
In case these chains will support trigger semantics
The text was updated successfully, but these errors were encountered: