Why is async_std::pin::Pin unstable?


And how does it differ from std::pin::Pin? Or, are they virtually the same?

1 Like

It's a reexport of the type in std. see source


The unstable doc comes from being wrapped by cfg_unstable!. I guess the authors don't want to commit to having that re-export in their API yet.

1 Like

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.