rust/crates/hir-expand/Cargo.toml

[package]
name = "hir-expand"
version = "0.0.0"
description = "TBD"
license = "MIT OR Apache-2.0"
edition = "2021"
rust-version = "1.57"

[lib]
doctest = false

[dependencies]
cov-mark = "2.0.0-pre.1"
tracing = "0.1.35"
either = "1.7.0"
rustc-hash = "1.1.0"
la-arena = { version = "0.3.0", path = "../../lib/la-arena" }
itertools = "0.10.3"
hashbrown = { version = "0.12.1", features = [
    "inline-more",
], default-features = false }
smallvec = { version = "1.9.0", features = ["const_new"] }

stdx = { path = "../stdx", version = "0.0.0" }
base-db = { path = "../base-db", version = "0.0.0" }
cfg = { path = "../cfg", version = "0.0.0" }
syntax = { path = "../syntax", version = "0.0.0" }
profile = { path = "../profile", version = "0.0.0" }
tt = { path = "../tt", version = "0.0.0" }
mbe = { path = "../mbe", version = "0.0.0" }
limit = { path = "../limit", version = "0.0.0" }

[dev-dependencies]
expect-test = "1.3.0"
start ra_hir_def crate 2019-10-29 03:15:51 -05:00			`[package]`
style: rename crates to kebab case 2022-04-29 09:29:24 -05:00			`name = "hir-expand"`
Rename ra_hir_expand -> hir_expand 2020-08-13 09:26:29 -05:00			`version = "0.0.0"`
Add description for crates that will be published 2020-08-24 06:06:30 -05:00			`description = "TBD"`
Add a license field to all the crates 2020-07-13 20:57:26 -05:00			`license = "MIT OR Apache-2.0"`
Migrate to edition 2021 2021-10-21 10:49:28 -05:00			`edition = "2021"`
Bump MSRV (1.57) 2021-12-15 14:49:48 -06:00			`rust-version = "1.57"`
start ra_hir_def crate 2019-10-29 03:15:51 -05:00
Disable doctests 2019-11-17 09:35:05 -06:00			`[lib]`
			`doctest = false`

start ra_hir_def crate 2019-10-29 03:15:51 -05:00			`[dependencies]`
fix: avoid pathological macro expansions Today, rust-analyzer (and rustc, and bat, and IntelliJ) fail badly on some kinds of maliciously constructed code, like a deep sequence of nested parenthesis. "Who writes 100k nested parenthesis" you'd ask? Well, in a language with macros, a run-away macro expansion might do that (see the added tests)! Such expansion can be broad, rather than deep, so it bypasses recursion check at the macro-expansion layer, but triggers deep recursion in parser. In the ideal world, the parser would just handle deeply nested structs gracefully. We'll get there some day, but at the moment, let's try to be simple, and just avoid expanding macros with unbalanced parenthesis in the first place. closes #9358 2021-08-09 08:06:49 -05:00			`cov-mark = "2.0.0-pre.1"`
internal: Bump Dependencies 2022-06-10 09:30:09 -05:00			`tracing = "0.1.35"`
Bump either 2022-07-03 01:42:41 -05:00			`either = "1.7.0"`
minor: Bump dependencies 2022-03-22 11:36:41 -05:00			`rustc-hash = "1.1.0"`
internal: vendor lsp-server 2022-05-14 05:33:48 -05:00			`la-arena = { version = "0.3.0", path = "../../lib/la-arena" }`
minor: Bump dependencies 2022-03-22 11:36:41 -05:00			`itertools = "0.10.3"`
internal: Bump Dependencies 2022-06-10 09:30:09 -05:00			`hashbrown = { version = "0.12.1", features = [`
Bump hashbrown 2022-01-21 11:44:03 -06:00			`"inline-more",`
			`], default-features = false }`
Use `SmallVec` to slightly shrink `ModPath` size 2022-07-06 12:49:05 -05:00			`smallvec = { version = "1.9.0", features = ["const_new"] }`
move expansion-related code to a separate crate 2019-10-29 06:55:39 -05:00
Improve proc macro errors a bit Distinguish between - there is no build data (for some reason?) - there is build data, but the cargo package didn't build a proc macro dylib - there is a proc macro dylib, but it didn't contain the proc macro we expected - the name did not resolve to any macro (this is now an unresolved_macro_call even for attributes) I changed the handling of disabled attribute macro expansion to immediately ignore the macro and report an unresolved_proc_macro, because otherwise they would now result in loud unresolved_macro_call errors. I hope this doesn't break anything. Also try to improve error ranges for unresolved_macro_call / macro_error by reusing the code for unresolved_proc_macro. It's not perfect but probably better than before. 2022-06-24 06:03:13 -05:00			`stdx = { path = "../stdx", version = "0.0.0" }`
style: rename crates to kebab case 2022-04-29 09:29:24 -05:00			`base-db = { path = "../base-db", version = "0.0.0" }`
Implement builtin `cfg!` macro 2021-03-10 12:43:03 -06:00			`cfg = { path = "../cfg", version = "0.0.0" }`
Add version to deps in cargo.toml 2020-08-24 03:25:19 -05:00			`syntax = { path = "../syntax", version = "0.0.0" }`
			`profile = { path = "../profile", version = "0.0.0" }`
			`tt = { path = "../tt", version = "0.0.0" }`
			`mbe = { path = "../mbe", version = "0.0.0" }`
Add `Limit` struct. Fixes #9286. 2021-07-10 15:49:17 -05:00			`limit = { path = "../limit", version = "0.0.0" }`
Actually check in fixup.rs 2022-02-07 13:30:28 -06:00
			`[dev-dependencies]`
internal: Bump Dependencies 2022-06-10 09:30:09 -05:00			`expect-test = "1.3.0"`