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

Tracking of planned breaking changes #614

Open
dvdsk opened this issue Sep 16, 2024 · 4 comments
Open

Tracking of planned breaking changes #614

dvdsk opened this issue Sep 16, 2024 · 4 comments
Labels
breaking Proposed change that would break the public API bug enhancement

Comments

@dvdsk
Copy link
Collaborator

dvdsk commented Sep 16, 2024

I want to gather all planned breaking changes and release them together with a porting/update guide and announcement on socials (for now rust user forum and reddit).

The changes are currently motivated by personal experience using rodio, and maintaining it. Before these changes are applied we hope to base them on user stories instead. Please if you use rodio or chose not describe your audio usecase here: #626.

This main post will be updated when new ideas are added. Each item links to an individual issues. If you wish to discuss a single change please do that in its linked issue.

@dvdsk dvdsk added bug enhancement breaking Proposed change that would break the public API labels Sep 16, 2024
@dvdsk dvdsk pinned this issue Sep 16, 2024
@dvdsk
Copy link
Collaborator Author

dvdsk commented Sep 16, 2024

@est31 Please let me know if you have other items that could be on here or object to some of the entries.

@dvdsk
Copy link
Collaborator Author

dvdsk commented Sep 28, 2024

@tomaka Would you be okay with the changes above? Thanks to est32 I have been able to maintain rodio for the past 9 months. Given the breaking nature of the changes listed I would like to have your blessing before I continue.

@tomaka
Copy link
Collaborator

tomaka commented Oct 18, 2024

Sorry for not answering, the way rodio works has left my mind a long time ago.
Nothing suggested above seems wrong to me.

If I had the time, I would personally go into a much deeper refactoring, such as removing entirely the Sink struct, or implement Source on Sink. IMO this struct comes from a fundamental misunderstanding of how the library is supposed to work (you're supposed to pull things to play through combining Sources, not push things). But given that I'm not going to do any work on the library any time soon, I would encourage you to consider my opinion as not relevant.

@dvdsk
Copy link
Collaborator Author

dvdsk commented Oct 18, 2024

Thank you very much for your comment. I share your sentiment on Sink. With some contributors we are considering ways to overhaul it. I will definitely consider removing it entirely. Sink currently functions as a easy way to use rodio without understanding source and to control playback without getting periodic_access. We might be able to think of something more elegant to fulfill that role.

@dvdsk dvdsk mentioned this issue Nov 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
breaking Proposed change that would break the public API bug enhancement
Projects
None yet
Development

No branches or pull requests

2 participants