rust/crates/paths/Cargo.toml

[package]
name = "paths"
version = "0.0.0"
description = "TBD"
license = "MIT OR Apache-2.0"
edition = "2021"
rust-version = "1.65"

[lib]
doctest = false

[dependencies]
# Adding this dep sadly puts a lot of rust-analyzer crates after the
# serde-derive crate. Even though we don't activate the derive feature here,
# someone else in the crate graph certainly does!
# serde = "1"
Introduce paths crate It's a good idea to distinguish between absolute and relative paths at the type level, to avoid accidental dependency on the cwd, which really shouldn't matter for rust-analyzer service 2020-06-14 07:08:28 -05:00			`[package]`
			`name = "paths"`
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"`
Migrate to edition 2021 2021-10-21 10:49:28 -05:00			`edition = "2021"`
:arrow_up: rust-analyzer 2022-11-23 09:24:03 -06:00			`rust-version = "1.65"`
Introduce paths crate It's a good idea to distinguish between absolute and relative paths at the type level, to avoid accidental dependency on the cwd, which really shouldn't matter for rust-analyzer service 2020-06-14 07:08:28 -05:00
			`[lib]`
			`doctest = false`
internal: make sure that proc macro machinery doesn't depend on cwd 2021-07-17 08:54:48 -05:00
			`[dependencies]`
internal: improve compilation critical path a bit 2021-08-28 14:03:06 -05:00			`# Adding this dep sadly puts a lot of rust-analyzer crates after the`
			`# serde-derive crate. Even though we don't activate the derive feature here,`
			`# someone else in the crate graph certainly does!`
			`# serde = "1"`