rust/crates/stdx/Cargo.toml

[package]
name = "stdx"
version = "0.0.0"
description = "TBD"
license = "MIT OR Apache-2.0"
authors = ["rust-analyzer developers"]
edition = "2018"

[lib]
doctest = false

[dependencies]
libc = "0.2.93"
backtrace = { version = "0.3.44", optional = true }
always-assert = { version = "0.1.2", features = ["log"] }
# Think twice before adding anything here

[target.'cfg(windows)'.dependencies]
miow = "0.3.6"
winapi = "0.3.9"

[features]
# Uncomment to enable for the whole crate graph
# default = [ "backtrace" ]
Start stdx This crate will hold everything to small to be worth publishing 2020-03-28 05:01:25 -05:00			`[package]`
			`name = "stdx"`
Rename ra_ide -> ide 2020-08-13 10:42:52 -05:00			`version = "0.0.0"`
Add description for crates that will be published 2020-08-24 06:06:30 -05:00			`description = "TBD"`
Rename ra_ide -> ide 2020-08-13 10:42:52 -05:00			`license = "MIT OR Apache-2.0"`
Start stdx This crate will hold everything to small to be worth publishing 2020-03-28 05:01:25 -05:00			`authors = ["rust-analyzer developers"]`
			`edition = "2018"`

			`[lib]`
			`doctest = false`

			`[dependencies]`
fix: no longer get stuck on windows reading both stdout & stderr is a common gotcha, you need to drain them concurrently to avoid deadlocks. Not sure why I didn't do the right thing from the start. Seems like I assumed the stderr is short? That's not the case when cargo spams `compiling xyz` messages 2021-04-20 08:06:20 -05:00			`libc = "0.2.93"`
Make printin the backtrace more convenient 2021-01-14 05:55:13 -06:00			`backtrace = { version = "0.3.44", optional = true }`
Cleanup decl_check 2021-02-05 09:09:45 -06:00			`always-assert = { version = "0.1.2", features = ["log"] }`
Start stdx This crate will hold everything to small to be worth publishing 2020-03-28 05:01:25 -05:00			`# Think twice before adding anything here`
Make printin the backtrace more convenient 2021-01-14 05:55:13 -06:00
fix: no longer get stuck on windows reading both stdout & stderr is a common gotcha, you need to drain them concurrently to avoid deadlocks. Not sure why I didn't do the right thing from the start. Seems like I assumed the stderr is short? That's not the case when cargo spams `compiling xyz` messages 2021-04-20 08:06:20 -05:00			`[target.'cfg(windows)'.dependencies]`
			`miow = "0.3.6"`
			`winapi = "0.3.9"`

Make printin the backtrace more convenient 2021-01-14 05:55:13 -06:00			`[features]`
			`# Uncomment to enable for the whole crate graph`
			`# default = [ "backtrace" ]`