Skip to content
This repository was archived by the owner on Aug 20, 2021. It is now read-only.

path to 1.0 #38

Closed
Susurrus opened this issue Nov 30, 2017 · 2 comments
Closed

path to 1.0 #38

Susurrus opened this issue Nov 30, 2017 · 2 comments

Comments

@Susurrus
Copy link

Ive been going through our dependencies and I saw that this crate is pre-1.0 and also didn't have a tracking issue for getting there. I wanted to post this to see if there was a plan for getting to 1.0. Considering how few issues have been posted with this crate and how often it's used, I'd think it would be pretty close to a 1.0, so wanted to check in here to see what the maintainers think.

@danielpclark
Copy link

See #28

@Susurrus
Copy link
Author

Susurrus commented Dec 1, 2017

Sorry, was looking for it in the title.

@Susurrus Susurrus closed this as completed Dec 1, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants