rust/src/librustc_errors/Cargo.toml

[package]
authors = ["The Rust Project Developers"]
name = "rustc_errors"
version = "0.0.0"

[lib]
name = "rustc_errors"
path = "lib.rs"
crate-type = ["dylib"]

[dependencies]
serialize = { path = "../libserialize" }
syntax_pos = { path = "../libsyntax_pos" }
rustc_data_structures = { path = "../librustc_data_structures" }
unicode-width = "0.1.4"
atty = "0.2"
termcolor = "0.3"
Move errors from libsyntax to its own crate 2016-06-21 18:08:13 -04:00			`[package]`
			`authors = ["The Rust Project Developers"]`
			`name = "rustc_errors"`
			`version = "0.0.0"`

			`[lib]`
			`name = "rustc_errors"`
			`path = "lib.rs"`
			`crate-type = ["dylib"]`

			`[dependencies]`
store typeck lints in the `TypeckTables` Otherwise they are a "hidden output" 2017-01-28 18:13:21 -05:00			`serialize = { path = "../libserialize" }`
rustbuild: Rewrite user-facing interface This commit is a rewrite of the user-facing interface to the rustbuild build system. The intention here is to make it much easier to compile/test the project without having to remember weird rule names and such. An overall view of the new interface is: # build everything ./x.py build # document everyting ./x.py doc # test everything ./x.py test # test libstd ./x.py test src/libstd # build libcore stage0 ./x.py build src/libcore --stage 0 # run stage1 run-pass tests ./x.py test src/test/run-pass --stage 1 The `src/bootstrap/bootstrap.py` script is now aliased as a top-level `x.py` script. This `x` was chosen to be both short and easily tab-completable (no collisions in that namespace!). The build system now accepts a "subcommand" of what to do next, the main ones being build/doc/test. Each subcommand then receives an optional list of arguments. These arguments are paths in the source repo of what to work with. That is, if you want to test a directory, you just pass that directory as an argument. The purpose of this rewrite is to do away with all of the arcane renames like "rpass" is the "run-pass" suite, "cfail" is the "compile-fail" suite, etc. By simply working with directories and files it's much more intuitive of how to run a test (just pass it as an argument). The rustbuild step/dependency management was also rewritten along the way to make this easy to work with and define, but that's largely just a refactoring of what was there before. The intention is that this support is extended for arbitrary files (e.g. `src/test/run-pass/my-test-case.rs`), but that isn't quite implemented just yet. Instead directories work for now but we can follow up with stricter path filtering logic to plumb through all the arguments. 2016-10-21 13:18:09 -07:00			`syntax_pos = { path = "../libsyntax_pos" }`
librustc_errors: Don't emit the same error message twice. 2017-10-25 15:01:06 +02:00			`rustc_data_structures = { path = "../librustc_data_structures" }`
When attempting to write str with single quote suggest double quotes 2017-12-10 23:35:53 -08:00			`unicode-width = "0.1.4"`
rustc: Migrate to `termcolor` crate from `term` This crate moves the compiler's error reporting to using the `termcolor` crate from crates.io. Previously rustc used a super-old version of the `term` crate in-tree which is basically unmaintained at this point, but Cargo has been using `termcolor` for some time now and tools like `rg` are using `termcolor` as well, so it seems like a good strategy to take! Note that the `term` crate remains in-tree for libtest. Changing libtest will be a bit tricky due to how the build works, but we can always tackle that later. cc #45728 2018-02-27 10:33:02 -08:00			`atty = "0.2"`
			`termcolor = "0.3"`