Merge pull request #28 from mrkkrp/analyze-macros

Analyze macros

Author: Calsign

Cargo.lock

@@ -10,6 +10,7 @@ path = "rust_parser/main.hs"
 [dependencies]
 cargo-lock = "11.0.0"
 cargo_toml = { version = "0.22.3", features = ["features"]}
-syn = { version = "2", features = ["full", "visit", "extra-traits"]}
 clap = { version = "4", features = ["derive"]}
 lazy_static = "1.5.0"
+proc-macro2 = "1"
+syn = { version = "2", features = ["full", "visit", "extra-traits"]}

Cargo.toml

@@ -136,8 +136,7 @@ is already in scope.
 This approach is fairly robust. Please see [`rust_parser/parser.rs`](./rust_parser/parser.rs) for
 implementation details and the [parser
 tests](https://github.com/Calsign/gazelle_rust/tree/main/rust_parser/test_data) for the range of
-cases covered. The only known case that is not handled is paths in macros like `println!`, which is
-quite tricky. (Derive macros are handled properly.)
+cases covered.
 
 For each dependency, gazelle\_rust identifies the crate in the project (or crate universe
 dependency) providing that crate name. gazelle\_rust raises an error if the crate could not be found

MODULE.bazel.lock

@@ -6,7 +6,10 @@ rust_library(
     name = "parser",
     srcs = ["parser.rs"],
     visibility = [":__subpackages__"],
-    deps = ["@crates//:syn"],
+    deps = [
+        "@crates//:proc-macro2",
+        "@crates//:syn",
+    ],
 )
 
 rust_library(