rust/xtask/Cargo.toml

[package]
edition = "2018"
name = "xtask"
version = "0.1.0"
authors = ["rust-analyzer developers"]
publish = false
license = "MIT OR Apache-2.0"

[lib]
doctest = false

[dependencies]
anyhow = "1.0.26"
flate2 = "1.0"
pico-args = "0.3.1"
proc-macro2 = "1.0.8"
quote = "1.0.2"
ungrammar = "1.9"
walkdir = "2.3.1"
write-json = "0.1.0"
xshell = "0.1"
# Avoid adding more dependencies to this crate
Move tools to a separate package 2018-02-03 03:51:06 -06:00			`[package]`
switch base crates to 2018 2018-10-15 12:00:54 -05:00			`edition = "2018"`
WIP: move to xtasks 2019-10-17 11:36:55 -05:00			`name = "xtask"`
Move tools to a separate package 2018-02-03 03:51:06 -06:00			`version = "0.1.0"`
Fix typo in Cargo.toml authors Fixes typo introduced in #782 2019-02-11 02:20:04 -06:00			`authors = ["rust-analyzer developers"]`
Move tools to a separate package 2018-02-03 03:51:06 -06:00			`publish = false`
Add a license field to all the crates 2020-07-13 20:57:26 -05:00			`license = "MIT OR Apache-2.0"`
Move tools to a separate package 2018-02-03 03:51:06 -06:00
Cleanup imports 2019-11-20 00:47:14 -06:00			`[lib]`
			`doctest = false`

Move tools to a separate package 2018-02-03 03:51:06 -06:00			`[dependencies]`
Update versions 2020-02-18 07:57:41 -06:00			`anyhow = "1.0.26"`
Gzip artifacts Co-authored-by: bjorn3 <bjorn3@users.noreply.github.com> Override miniz_oxide to build it with optimizations Building this crate with optimizations decreases the gzipping part of `cargo xtask dist` from `30-40s` down to `3s`, the overhead for `rustc` to apply optimizations is miserable on this background 2020-06-21 07:58:34 -05:00			`flate2 = "1.0"`
Switch to ungrammar from ast_src The primary advantage of ungrammar is that it (eventually) allows one to describe concrete syntax tree structure -- with alternatives and specific sequence of tokens & nodes. That should be re-usable for: * generate `make` calls * Rust reference * Hypothetical parser's evented API We loose doc comments for the time being unfortunately. I don't think we should add support for doc comments to ungrammar -- they'll make grammar file hard to read. We might supply docs as out-of band info, or maybe just via a reference, but we'll think about that once things are no longer in flux 2020-07-29 08:45:23 -05:00			`pico-args = "0.3.1"`
			`proc-macro2 = "1.0.8"`
			`quote = "1.0.2"`
Wrap remaining self/super/crate in Name{Ref} 2021-01-15 14:07:38 -06:00			`ungrammar = "1.9"`
Switch to ungrammar from ast_src The primary advantage of ungrammar is that it (eventually) allows one to describe concrete syntax tree structure -- with alternatives and specific sequence of tokens & nodes. That should be re-usable for: * generate `make` calls * Rust reference * Hypothetical parser's evented API We loose doc comments for the time being unfortunately. I don't think we should add support for doc comments to ungrammar -- they'll make grammar file hard to read. We might supply docs as out-of band info, or maybe just via a reference, but we'll think about that once things are no longer in flux 2020-07-29 08:45:23 -05:00			`walkdir = "2.3.1"`
Node-ify lifetimes 2020-12-15 12:23:51 -06:00			`write-json = "0.1.0"`
Switch from not_bash to xshell 2020-10-16 12:46:03 -05:00			`xshell = "0.1"`
Document xtask has few deps invariant 2020-08-14 10:30:16 -05:00			`# Avoid adding more dependencies to this crate`