You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 3, 2020. It is now read-only.
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: