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.
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
feat(internal): new
prepareAttenuator
leveraging callbacks #7586feat(internal): new
prepareAttenuator
leveraging callbacks #7586Changes from all commits
55599df
884fa3b
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
What is the use case for making target optional (e.g.,
makeAttenuator({ target: undefined, overrides })
)?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.
If you want to compose an object entirely out of callbacks, you don't need a default target.
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.
Should we encourage use of
makeAttenuator
for composing an object from callbacks? I would expect not, as opposed to e.g.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.
(Aside from legacy...)
Now that we have attenuators, when would we ever use callbacks? AFAICT, attenuators are just better. If so, perhaps we should try to phase out callbacks over time.
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 don't see how attenuators supplant callbacks. Thanks to callbacks you can compose a new object of a given shape from different existing objects. They are complimentary.
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.
Should these errors be more similar? Can they be?
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.
The first is an engine-specific TypeError for which
not a function
is the terse message you get whenatE.m3
is not defined (in Node.js for this test).The second is a rejection by the HandledPromise shim that contains much more specific information, such as the methods that do exist, and the type of
target
. We could change this one, but its format is pretty deeply entrenched in Agoric SDK unit tests.