Skip to content
This repository has been archived by the owner on Mar 3, 2020. It is now read-only.

Is anyone interested in maintaining this crate? #109

Open
withoutboats opened this issue Aug 6, 2018 · 0 comments
Open

Is anyone interested in maintaining this crate? #109

withoutboats opened this issue Aug 6, 2018 · 0 comments

Comments

@withoutboats
Copy link
Collaborator

withoutboats commented Aug 6, 2018

This crate uses the proc-macro APIs, which have been going through a lot of churn as they prepare for stabilization. As a result, its been broken a lot - more often than not probably - on recent nightlies.

Now that async/await is being implemented in the compiler, this is basically a deprecated legacy API. As a result, my focus (and Alex's) has not been on getting this crate to build again, leaving it broken for too long at a time. But of course there are definitely users who depend on this crate and can't upgrade to the built-in feature yet.

So I'm wondering: does anyone want to take on responsibility for keeping this code green? The proc macro APIs are supposed to stabilize soon, so hopefully once that happens it will go back to being fairly stable.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant