Skip to content
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

send_future is no longer needed #792

Closed
hgzimmerman opened this issue Dec 9, 2019 · 0 comments · Fixed by #799
Closed

send_future is no longer needed #792

hgzimmerman opened this issue Dec 9, 2019 · 0 comments · Fixed by #799
Milestone

Comments

@hgzimmerman
Copy link
Member

Description

I'm submitting a feature request
Put your description here

@jstarry and I have talked about removing the send_future function on ComponentLink. Our current consensus revolves around it being possible to implement this using the existing send_message function on that datatype to accomplish the same thing.

Yewtil, the utilities crate for Yew already has a replacement ready for its next release that does the same thing and just requires importing a trait to use a send_future method.

I suggest that we remove this feature from the main crate, and point users towards the utility crate.
Because yewtil is heavily feature-gated, users are free to pick and choose which features to enable, so there shouldn't be any unwanted overhead besides having to import that trait.

@jstarry jstarry changed the title Remove send_future send_future is no longer needed Dec 10, 2019
@jstarry jstarry added this to the 0.11 milestone Dec 10, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants