exa does not compile with Rust 1.0 about exa

[ogham]

Sadly not :(

Don't get me wrong, I'd love to be able to compile with Rust 1.0! But unfortunately at the moment I'm using a lot of unstable APIs that only work with the nightly:

• I need the fs_ext and fs_mode features to determine file permissions;
• I need the file_type feature to determine file types;
• I need the metadata_ext and raw_ext features to get things like the user and group numbers, and modification date;
• I need the symlink_metadata feature to handle getting info on symlinks correctly.

So it's not just a case of using a few features from collections or core that I might be able to work around - a version without these unstable features would have a significant loss in functionality.

The way I'm working around it is by using multirust to have the stable, beta, and nightly channels installed side-by-side. And until these features become stable, this might be the best you can do.

[FrancoisBlavoet]

Thanks for clearing that up.
Too bad ! Well, in the meantime, one can always download the last release for easy installation.

[ogham]

Too bad indeed. I'm going to do a new release in the next few days because the current one is missing a few features!

[ogham]

Minor update on this! There are currently six things in exa that require a nightly compiler:

• The iter_arith, convert, fs_mode, slice_splits, and vec_resize feature flags. All of these use recently-added APIs which are likely to be stabilised in the near future.
• The scoped_threadpool crate, which requires an unsafe block to work on stable.

So we're past the point where exa is using experimental stuff, and are just waiting for things to settle down.

[ogham]

Rust 1.4.0 allows safe scoped threadpools, so we're down to five things that require a nightly compiler!

[ogham]

Fixed in #85!