-
Notifications
You must be signed in to change notification settings - Fork 1
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
multinode: remove generic result type #10
Conversation
This looks fine, is there an associated PR for the main chainlink repo? |
6766da3
to
efd7093
Compare
efd7093
to
9783fa9
Compare
9783fa9
to
5012d4f
Compare
type SendTxResult interface { | ||
Code() SendTxReturnCode | ||
Error() error | ||
type sendTxResult[RESULT any] struct { |
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.
Instead of requiring this interface to be implemented by each user, we can use a struct internally, and multivalue returns with a plain generic result value. This sheds a ton of boilerplate, including the constructor function.
While investigating
SendTxReturnCode
I noticed that this exported and generic result wrapper type is not really necessary.Supports