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

Polish backon vision: What is backon and what are its future goals? #98

Closed
Xuanwo opened this issue Aug 22, 2024 · 3 comments
Closed

Polish backon vision: What is backon and what are its future goals? #98

Xuanwo opened this issue Aug 22, 2024 · 3 comments

Comments

@Xuanwo
Copy link
Owner

Xuanwo commented Aug 22, 2024

I started backon as an alternative to backoff. I love its API design and am happy to see it being used in many production areas. As part of our 1.0 plan, I believe the first step is to clarify what backon is and what its future goals are.

@Xuanwo Xuanwo mentioned this issue Aug 22, 2024
4 tasks
@Xuanwo
Copy link
Owner Author

Xuanwo commented Aug 23, 2024

Backon should be correct, simple, and zero-cost. It should feel like a native feature of Rust. It should be the default choice, similar to serde in Rust: when users want to retry something, they should immediately think of using Backon.

@Xuanwo
Copy link
Owner Author

Xuanwo commented Aug 23, 2024

Backon should be a runtime agnostic solution that can operate on any asynchronous runtime.

@Xuanwo
Copy link
Owner Author

Xuanwo commented Aug 23, 2024

Backon should be available on any platform that supports Rust.

Maybe even no-std? Can we?

@Xuanwo Xuanwo closed this as completed Aug 26, 2024
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

No branches or pull requests

1 participant