rust/crates/ra_prof/Cargo.toml

[package]
edition = "2018"
name = "ra_prof"
version = "0.1.0"
authors = ["rust-analyzer developers"]
publish = false

[dependencies]
once_cell = "0.2.0"
itertools = "0.8.0"
backtrace = "0.3.28"
cpuprofiler = { version = "0.0.3", optional = true }
jemallocator = { version = "0.3.2", optional = true }
jemalloc-ctl = { version = "0.3.2", optional = true }


[features]
jemalloc = [ "jemallocator", "jemalloc-ctl" ]
profiling crate first draft 2019-03-27 10:09:51 -05:00			`[package]`
			`edition = "2018"`
			`name = "ra_prof"`
			`version = "0.1.0"`
			`authors = ["rust-analyzer developers"]`
			`publish = false`

			`[dependencies]`
switch to once_cell from lazy_static 2019-05-07 12:54:33 -05:00			`once_cell = "0.2.0"`
better profilig 2019-05-21 16:00:58 -05:00			`itertools = "0.8.0"`
add couple of debug utils 2019-06-03 16:25:43 -05:00			`backtrace = "0.3.28"`
add cpuprofile to ra_prof Now, one can use `let _p = ra_prof::cpu_profiler()` to capture profile of a block of code. This is not an out of the box experience, as that relies on gperfools See the docs on https://github.com/AtheMathmo/cpuprofiler for more! 2019-06-26 03:11:28 -05:00			`cpuprofiler = { version = "0.0.3", optional = true }`
jemallocator 0.3 2019-07-17 09:58:17 -05:00			`jemallocator = { version = "0.3.2", optional = true }`
			`jemalloc-ctl = { version = "0.3.2", optional = true }`
Move memory usage statistics to ra_prof 2019-06-30 05:30:17 -05:00

			`[features]`
			`jemalloc = [ "jemallocator", "jemalloc-ctl" ]`