-
Notifications
You must be signed in to change notification settings - Fork 3
feat(signet-orders): provide traits #170
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
Conversation
| fn submit_order( | ||
| &self, | ||
| order: SignedOrder, | ||
| ) -> impl Future<Output = Result<(), Self::Error>> + Send; |
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 this be AFIT? or do we want to mandate Send?
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.
Hmm - good question! I defaulted to mandating Send just because that's what I'm generally used to (multi-threaded tokio runtime specifically). I'm not sure if there are expected use cases where this would be a problem, but if not, I'd lean towards mandating Send.
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.
in my experience the main place this causes problems is use in wasm, which is not a priority for use. I'm fine mandating Send
Evalir
left a comment
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.
lgtm

This PR introduces three new traits to support submitting orders or bundles and fetching orders.