2014-12-02 09:20:48 -05:00
|
|
|
// Copyright 2014 The Rust Project Developers. See the COPYRIGHT
|
|
|
|
// file at the top-level directory of this distribution and at
|
|
|
|
// http://rust-lang.org/COPYRIGHT.
|
|
|
|
//
|
|
|
|
// Licensed under the Apache License, Version 2.0 <LICENSE-APACHE or
|
|
|
|
// http://www.apache.org/licenses/LICENSE-2.0> or the MIT license
|
|
|
|
// <LICENSE-MIT or http://opensource.org/licenses/MIT>, at your
|
|
|
|
// option. This file may not be copied, modified, or distributed
|
|
|
|
// except according to those terms.
|
|
|
|
|
2015-02-26 21:00:43 -08:00
|
|
|
#![deny(warnings)]
|
|
|
|
|
2015-01-22 18:22:03 -08:00
|
|
|
#![feature(core)]
|
2015-02-26 21:00:43 -08:00
|
|
|
#![feature(exit_status)]
|
2015-01-22 18:22:03 -08:00
|
|
|
#![feature(rustdoc)]
|
std: Stabilize the `fs` module
This commit performs a stabilization pass over the `std::fs` module now that
it's had some time to bake. The change was largely just adding `#[stable]` tags,
but there are a few APIs that remain `#[unstable]`.
The following apis are now marked `#[stable]`:
* `std::fs` (the name)
* `File`
* `Metadata`
* `ReadDir`
* `DirEntry`
* `OpenOptions`
* `Permissions`
* `File::{open, create}`
* `File::{sync_all, sync_data}`
* `File::set_len`
* `File::metadata`
* Trait implementations for `File` and `&File`
* `OpenOptions::new`
* `OpenOptions::{read, write, append, truncate, create}`
* `OpenOptions::open` - this function was modified, however, to not attempt to
reject cross-platform openings of directories. This means that some platforms
will succeed in opening a directory and others will fail.
* `Metadata::{is_dir, is_file, len, permissions}`
* `Permissions::{readonly, set_readonly}`
* `Iterator for ReadDir`
* `DirEntry::path`
* `remove_file` - like with `OpenOptions::open`, the extra windows code to
remove a readonly file has been removed. This means that removing a readonly
file will succeed on some platforms but fail on others.
* `metadata`
* `rename`
* `copy`
* `hard_link`
* `soft_link`
* `read_link`
* `create_dir`
* `create_dir_all`
* `remove_dir`
* `remove_dir_all`
* `read_dir`
The following apis remain `#[unstable]`.
* `WalkDir` and `walk` - there are many methods by which a directory walk can be
constructed, and it's unclear whether the current semantics are the right
ones. For example symlinks are not handled super well currently. This is now
behind a new `fs_walk` feature.
* `File::path` - this is an extra abstraction which the standard library
provides on top of what the system offers and it's unclear whether we should
be doing so. This is now behind a new `file_path` feature.
* `Metadata::{accessed, modified}` - we do not currently have a good
abstraction for a moment in time which is what these APIs should likely be
returning, so these remain `#[unstable]` for now. These are now behind a new
`fs_time` feature
* `set_file_times` - like with `Metadata::accessed`, we do not currently have
the appropriate abstraction for the arguments here so this API remains
unstable behind the `fs_time` feature gate.
* `PathExt` - the precise set of methods on this trait may change over time and
some methods may be removed. This API remains unstable behind the `path_ext`
feature gate.
* `set_permissions` - we may wish to expose a more granular ability to set the
permissions on a file instead of just a blanket "set all permissions" method.
This function remains behind the `fs` feature.
The following apis are now `#[deprecated]`
* The `TempDir` type is now entirely deprecated and is [located on
crates.io][tempdir] as the `tempdir` crate with [its source][github] at
rust-lang/tempdir.
[tempdir]: https://crates.io/crates/tempdir
[github]: https://github.com/rust-lang/tempdir
The stability of some of these APIs has been questioned over the past few weeks
in using these APIs, and it is intentional that the majority of APIs here are
marked `#[stable]`. The `std::fs` module has a lot of room to grow and the
material is [being tracked in a RFC issue][rfc-issue].
[rfc-issue]: https://github.com/rust-lang/rfcs/issues/939
[breaking-change]
2015-03-03 19:18:29 -08:00
|
|
|
#![feature(rustc_private)]
|
2015-03-18 09:36:18 -07:00
|
|
|
#![feature(path_relative_from)]
|
2014-12-02 09:20:48 -05:00
|
|
|
|
|
|
|
extern crate rustdoc;
|
std: Stabilize the `fs` module
This commit performs a stabilization pass over the `std::fs` module now that
it's had some time to bake. The change was largely just adding `#[stable]` tags,
but there are a few APIs that remain `#[unstable]`.
The following apis are now marked `#[stable]`:
* `std::fs` (the name)
* `File`
* `Metadata`
* `ReadDir`
* `DirEntry`
* `OpenOptions`
* `Permissions`
* `File::{open, create}`
* `File::{sync_all, sync_data}`
* `File::set_len`
* `File::metadata`
* Trait implementations for `File` and `&File`
* `OpenOptions::new`
* `OpenOptions::{read, write, append, truncate, create}`
* `OpenOptions::open` - this function was modified, however, to not attempt to
reject cross-platform openings of directories. This means that some platforms
will succeed in opening a directory and others will fail.
* `Metadata::{is_dir, is_file, len, permissions}`
* `Permissions::{readonly, set_readonly}`
* `Iterator for ReadDir`
* `DirEntry::path`
* `remove_file` - like with `OpenOptions::open`, the extra windows code to
remove a readonly file has been removed. This means that removing a readonly
file will succeed on some platforms but fail on others.
* `metadata`
* `rename`
* `copy`
* `hard_link`
* `soft_link`
* `read_link`
* `create_dir`
* `create_dir_all`
* `remove_dir`
* `remove_dir_all`
* `read_dir`
The following apis remain `#[unstable]`.
* `WalkDir` and `walk` - there are many methods by which a directory walk can be
constructed, and it's unclear whether the current semantics are the right
ones. For example symlinks are not handled super well currently. This is now
behind a new `fs_walk` feature.
* `File::path` - this is an extra abstraction which the standard library
provides on top of what the system offers and it's unclear whether we should
be doing so. This is now behind a new `file_path` feature.
* `Metadata::{accessed, modified}` - we do not currently have a good
abstraction for a moment in time which is what these APIs should likely be
returning, so these remain `#[unstable]` for now. These are now behind a new
`fs_time` feature
* `set_file_times` - like with `Metadata::accessed`, we do not currently have
the appropriate abstraction for the arguments here so this API remains
unstable behind the `fs_time` feature gate.
* `PathExt` - the precise set of methods on this trait may change over time and
some methods may be removed. This API remains unstable behind the `path_ext`
feature gate.
* `set_permissions` - we may wish to expose a more granular ability to set the
permissions on a file instead of just a blanket "set all permissions" method.
This function remains behind the `fs` feature.
The following apis are now `#[deprecated]`
* The `TempDir` type is now entirely deprecated and is [located on
crates.io][tempdir] as the `tempdir` crate with [its source][github] at
rust-lang/tempdir.
[tempdir]: https://crates.io/crates/tempdir
[github]: https://github.com/rust-lang/tempdir
The stability of some of these APIs has been questioned over the past few weeks
in using these APIs, and it is intentional that the majority of APIs here are
marked `#[stable]`. The `std::fs` module has a lot of room to grow and the
material is [being tracked in a RFC issue][rfc-issue].
[rfc-issue]: https://github.com/rust-lang/rfcs/issues/939
[breaking-change]
2015-03-03 19:18:29 -08:00
|
|
|
extern crate rustc_back;
|
2014-12-02 09:20:48 -05:00
|
|
|
|
2015-02-16 16:04:02 +02:00
|
|
|
use std::env;
|
2015-02-26 21:00:43 -08:00
|
|
|
use std::error::Error;
|
2014-12-02 09:20:48 -05:00
|
|
|
use subcommand::Subcommand;
|
|
|
|
use term::Term;
|
|
|
|
|
|
|
|
mod term;
|
|
|
|
mod error;
|
|
|
|
mod book;
|
|
|
|
|
|
|
|
mod subcommand;
|
|
|
|
mod help;
|
|
|
|
mod build;
|
|
|
|
mod serve;
|
|
|
|
mod test;
|
|
|
|
|
|
|
|
mod css;
|
2015-01-12 16:51:31 -08:00
|
|
|
mod javascript;
|
2014-12-02 09:20:48 -05:00
|
|
|
|
|
|
|
#[cfg(not(test))] // thanks #12327
|
|
|
|
fn main() {
|
|
|
|
let mut term = Term::new();
|
2015-02-16 16:04:02 +02:00
|
|
|
let cmd: Vec<_> = env::args().collect();
|
2014-12-02 09:20:48 -05:00
|
|
|
|
2015-02-15 23:40:56 +08:00
|
|
|
if cmd.len() <= 1 {
|
2014-12-02 09:20:48 -05:00
|
|
|
help::usage()
|
|
|
|
} else {
|
2015-02-23 00:20:42 +02:00
|
|
|
match subcommand::parse_name(&cmd[1][..]) {
|
2014-12-02 09:20:48 -05:00
|
|
|
Some(mut subcmd) => {
|
2015-02-26 21:00:43 -08:00
|
|
|
match subcmd.parse_args(&cmd[..cmd.len()-1]) {
|
2014-12-02 09:20:48 -05:00
|
|
|
Ok(_) => {
|
|
|
|
match subcmd.execute(&mut term) {
|
|
|
|
Ok(_) => (),
|
2015-01-09 20:25:45 +11:00
|
|
|
Err(err) => {
|
2015-02-26 21:00:43 -08:00
|
|
|
term.err(&format!("error: {}", err));
|
2015-01-09 20:25:45 +11:00
|
|
|
}
|
2014-12-02 09:20:48 -05:00
|
|
|
}
|
|
|
|
}
|
|
|
|
Err(err) => {
|
|
|
|
println!("{}", err.description());
|
|
|
|
println!("");
|
|
|
|
subcmd.usage();
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
None => {
|
|
|
|
println!("Unrecognized command '{}'.", cmd[1]);
|
|
|
|
println!("");
|
|
|
|
help::usage();
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|