Skip to content

Looking forward to a 1.0 release #192

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

Closed
sunfishcode opened this issue Oct 22, 2021 · 3 comments
Closed

Looking forward to a 1.0 release #192

sunfishcode opened this issue Oct 22, 2021 · 3 comments

Comments

@sunfishcode
Copy link
Member

cap-std's coverage of std's fs, net, and time APIs is roughly as complete as it can be, and has been fairly stable for some time now. The one upcoming breaking change I'm aware of is that once the I/O safety features in std are stabilized, cap-std should use those and remove its OwnsRaw trait impls. That may be a good occasion to make a 1.0 semver release.

I could imagine potential future changes, such as changing the way the Pool type in cap_std::net works, but there's always 2.0 and beyond.

If there's anything that should go into a 1.0 release, please post about it!

@dckc
Copy link

dckc commented Nov 26, 2021

nice to see this maturing!

The current ambient_authority approach looks pretty good. I wonder if there are better ways to use it in the examples: #206.

@sunfishcode
Copy link
Member Author

Another future change will be when the I/O safety types OwnedFd, BorrowedFd, etc. are stabilized in std, and we can use them instead of using the io-lifetimes versions of them.

@sunfishcode
Copy link
Member Author

Closing this out, as this is now tracked in #272.

Changes like changing cap_std::net's Pool mechanism are still open for consideration, but are significant enough that we can think about those for a 2.0 release.

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

2 participants