Exploratory PR for adding pullable's as suggested in issue #581 #609
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
staltz
force-pushed
the
master
branch
2 times, most recently
from
19355d6
to
61f81cf
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is an exploratory PR to test idea in issue #581, proving that no major changes needed for bolting on a support for first class (in cycle) objects that carry pull-ing.
There are already
PullableValue's that can act as memory cells, and a more generalPullablethat can be used for implementing services that are consumed as pulls, while being written in a normal cycle push flow, illustrating that consumer's pull is producer's push.make test runfor the packagerunI'm modifying. All existing test run, except for lint complaining that new index.ts is 330-something lines, greater than 300 lines.