-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
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
react: Update tests to v2.0.0 #1346
Merged
Merged
Changes from 1 commit
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
bc89832
react: re-implement according to canonical data
mrcfps 307b3f1
react: update tests to v1.2.0
mrcfps 4d1eedb
react: correct test method name
mrcfps 513bc6a
react: fix example solution py2-compatibility
mrcfps abb7e0a
react: refactor callbacks into pure functions
mrcfps 42eccbf
Merge upstream/master into react-1257
mrcfps 688a30c
react: update tests to v2.0.0
mrcfps 71214fb
Merge branch 'master' into react-1257
cmccandless File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure that I like
expect_callback_values
being a member ofComputeCell
...What do you think about something like this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You mean convert
callback
tocallback_buffer
, and keep outputs of callbacks in the buffer? If so, I guess problem specification of this exercise should be changed, too.My justification for
expect_callback_values
being a member ofComputeCell
is thatComputeCell
seems to be acting as a host for callbacks to be attached to and detached from. Or you can imagine callbacks as plugins for theComputeCell
, so trying to obtain output values of a callback is like reading the state of a plugin.However, these are just analogies. Insights are welcome.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are discussions on rewording the canonical-data, but I don't think that semantic changes are necessary to it.
Close: this is more of a publisher/subscriber scenario. The
ComputerCell
"publishes" new values by calling the registered callbacks. The callback is the subscription mechanism. The publisher doesn't care what the subscriber object is or how it uses the published data, and has no access to it. In a practical use case, if one were trying to use the solution for this exercise to perform calculations, they might simply useoutput.add_callback(lambda v: print(v))
I don't remember if I linked @petertseng's comment before (exercism/problem-specifications#1194 (comment)), but it's a good in-context note on what a callback is/should be.