It is interesting to see here the destiny operator, in which we have been using component composition description language for a long time.
A few examples of how we declare object methods (channels):
name \Jin
This is a method that returns a constant string (one way channel).
name?val \Jin
This is the same, but the meaning can be changed (singal in your terminology and two-way channel in ours).
Now the operator of destiny:
greeting / \Mr. <= name
There is already a derived method that returns an array from a constant string and the values of another method.
And now, the most interesting thing is the bidirectional channel:
title?val <=> name?val
We can read and write in 'title' without even knowing that we are actually working with 'name'.
And then there is the reverse destiny operator:
name => title
It may seem that this is the same as the normal destiny operator, but it matters when linking components to each other:
sub / <= Input $mol_string value => name <= Output $mol_paragraph title <= name
Now the Output directly uses the value from the Input, and we control it through the "name" channel.
Output
Input
And yes, Input and Output is channels too which returns cached instance of other components.
Here you can see the generated TS code.
Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.
Hide child comments as well
Confirm
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
It is interesting to see here the destiny operator, in which we have been using component composition description language for a long time.
A few examples of how we declare object methods (channels):
This is a method that returns a constant string (one way channel).
This is the same, but the meaning can be changed (singal in your terminology and two-way channel in ours).
Now the operator of destiny:
There is already a derived method that returns an array from a constant string and the values of another method.
And now, the most interesting thing is the bidirectional channel:
We can read and write in 'title' without even knowing that we are actually working with 'name'.
And then there is the reverse destiny operator:
It may seem that this is the same as the normal destiny operator, but it matters when linking components to each other:
Now the
Output
directly uses the value from theInput
, and we control it through the "name" channel.And yes,
Input
andOutput
is channels too which returns cached instance of other components.Here you can see the generated TS code.