docs: add pathf_export macro to roadmap

1 files changed, 25 insertions, 0 deletions

diff --git a/docs/dev/pages/issues/0.5.0-roadmap.md b/docs/dev/pages/issues/0.5.0-roadmap.md
index 0312193..5238cae 100644
--- a/docs/dev/pages/issues/0.5.0-roadmap.md
+++ b/docs/dev/pages/issues/0.5.0-roadmap.md
@@ -108,6 +108,31 @@ version = "0.4.0"
 features = [ "build", "pathf" ] # No `dispatch_tree` feature; `pathf` no longer needs to consider its branches
 ```
  
+8. **Feature:** A new macro designed for `pathf`: `#[pathf_export(type::TypePath)]`
+
+`pathf` has been around since 0.2.0 and has worked well for a long time, with many edge cases resolved. However, it still lacks an escape hatch — "when certain indirect expansions cannot be recognized by `pathf`, how can we assist its inference?"
+
+I plan to introduce a new attribute macro to supplement `pathf`'s path inference.
+
+```rust
+#[macro_export]
+macro_rules! repack {
+    ($name:ident) => {
+        // Ignored! This section cannot be parsed by pathf.
+        #[mingling::macros::pathf_ignore]
+        #[derive(mingling::Grouped)]
+        pub struct $name;
+    };
+}
+ 
+// The expansion contains macros that need to be parsed by pathf
+#[pathf_export(MyType)] // Explicitly specified to assist pathf's inference
+repack!(MyType);
+```
+ 
+> [!Note]
+> Haha, hopefully we'll never have to use it.
+
 <p align="center" style="font-size: 0.85em; color: gray;">
     Written by @Weicao-CatilGrass
 </p>