dbb702cfc1
FragmentKind played two roles: * entry point to the parser * syntactic category of a macro call These are different use-cases, and warrant different types. For example, macro can't expand to visibility, but we have such fragment today. This PR introduces `ExpandsTo` enum to separate this two use-cases. I suspect we might further split `FragmentKind` into `$x:specifier` enum specific to MBE, and a general parser entry point, but that's for another PR!
30 lines
733 B
TOML
30 lines
733 B
TOML
[package]
|
|
name = "hir_expand"
|
|
version = "0.0.0"
|
|
description = "TBD"
|
|
license = "MIT OR Apache-2.0"
|
|
edition = "2018"
|
|
|
|
[lib]
|
|
doctest = false
|
|
|
|
[dependencies]
|
|
cov-mark = "2.0.0-pre.1"
|
|
tracing = "0.1"
|
|
either = "1.5.3"
|
|
rustc-hash = "1.0.0"
|
|
la-arena = { version = "0.2.0", path = "../../lib/arena" }
|
|
itertools = "0.10.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]
|
|
test_utils = { path = "../test_utils" }
|
|
expect-test = "1.1"
|