rust-analyzer/crates/ra_cargo_watch/Cargo.toml

[package]
edition = "2018"
name = "ra_cargo_watch"
version = "0.1.0"
authors = ["rust-analyzer developers"]

[dependencies]
crossbeam-channel = "0.4"
lsp-types = { version = "0.70.0", features = ["proposed"] }
log = "0.4.3"
cargo_metadata = "0.9.1"
jod-thread = "0.1.0"
parking_lot = "0.10.0"
serde_json = "1.0.45"

[dev-dependencies]
insta = "0.13.0"
serde_json = "1.0"
Move cargo watch functionality to separate crate 2019-12-27 10:10:07 +00:00			`[package]`
			`edition = "2018"`
			`name = "ra_cargo_watch"`
			`version = "0.1.0"`
			`authors = ["rust-analyzer developers"]`

			`[dependencies]`
			`crossbeam-channel = "0.4"`
Update crates 2020-01-22 20:40:35 +00:00			`lsp-types = { version = "0.70.0", features = ["proposed"] }`
Move cargo watch functionality to separate crate 2019-12-27 10:10:07 +00:00			`log = "0.4.3"`
			`cargo_metadata = "0.9.1"`
			`jod-thread = "0.1.0"`
			`parking_lot = "0.10.0"`
Parse cargo output a line at a time. We previously used serde's stream deserializer to read json blobs from the cargo output. It has an issue though: If the deserializer encounters invalid input, it gets stuck reporting the same error again and again because it is unable to foward over the input until it reaches a new valid object. Reading a line at a time and manually deserializing fixes this issue, because cargo makes sure to only outpu one json blob per line, so should we encounter invalid input, we can just skip a line and continue. The main reason this would happen is stray printf-debugging in procedural macros, so we still report that an error occured, but we handle it gracefully now. Fixes #2935 2020-01-29 12:40:27 +00:00			`serde_json = "1.0.45"`
Move cargo watch functionality to separate crate 2019-12-27 10:10:07 +00:00
			`[dev-dependencies]`
Update crates 2020-01-26 15:46:45 +00:00			`insta = "0.13.0"`
Move cargo watch functionality to separate crate 2019-12-27 10:10:07 +00:00			`serde_json = "1.0"`