Skip to content
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

fs: move into tokio #1672

Merged
merged 3 commits into from
Oct 21, 2019
Merged

fs: move into tokio #1672

merged 3 commits into from
Oct 21, 2019

Conversation

carllerche
Copy link
Member

A step towards collapsing Tokio sub crates into a single tokio
crate (#1318).

The fs implementation is now provided by the main tokio crate. The
fs functionality may still be excluded from the build by skipping the
fs feature flag.

A step towards collapsing Tokio sub crates into a single `tokio`
crate (#1318).

The `fs` implementation is now provided by the main `tokio` crate. The
`fs` functionality may still be excluded from the build by skipping the
`fs` feature flag.
@davidbarsky
Copy link
Member

I think the reduction in maintenance burden is a win, but I'm curious as to what the compile times are with cargo build -Ztimings before and after this change.

@carllerche carllerche merged commit 978013a into master Oct 21, 2019
@carllerche carllerche deleted the flatten-fs branch October 22, 2019 18:13
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

Successfully merging this pull request may close these issues.

3 participants