aboutsummaryrefslogtreecommitdiff
path: root/docs/dev/pages
diff options
context:
space:
mode:
Diffstat (limited to 'docs/dev/pages')
-rw-r--r--docs/dev/pages/issues/_add-picker2.md (renamed from docs/dev/pages/issues/add-picker2.md)12
-rw-r--r--docs/dev/pages/issues/_remove-r-print-macro.md (renamed from docs/dev/pages/issues/remove-r-print-macro.md)6
-rw-r--r--docs/dev/pages/issues/_the-mod-pathfinder.md (renamed from docs/dev/pages/issues/the-mod-pathfinder.md)6
3 files changed, 18 insertions, 6 deletions
diff --git a/docs/dev/pages/issues/add-picker2.md b/docs/dev/pages/issues/_add-picker2.md
index a2b5a10..fcd6786 100644
--- a/docs/dev/pages/issues/add-picker2.md
+++ b/docs/dev/pages/issues/_add-picker2.md
@@ -1,8 +1,12 @@
-<h1 align="center">The Picker2 Arguments Parser</h1>
+<h1 align="center">[Solved] The Picker2 Arguments Parser</h1>
<p align="center">
A smarter, faster alternative to Picker
</p>
+> [!NOTE]
+>
+> This issue has been fully resolved and is thus archived for preservation.
+
## Intro
Mingling's `parser` feature is a temporary argument parsing solution created in the early stages of the project. While it can handle basic argument parsing tasks, its functionality is incomplete and has many limitations.
@@ -94,7 +98,7 @@ pub struct PickerResult<Tuple> {
- [x] Added `parselib` providing parsing logic
- [x] Added `Pickable` for extensibility
- [x] Comprehensive testing!
- - [ ] Improve documentation
+ - [x] Improve documentation
- [x] Add examples
- - [ ] Update README
-- [ ] Complete
+ - [x] Update README
+- [x] Complete
diff --git a/docs/dev/pages/issues/remove-r-print-macro.md b/docs/dev/pages/issues/_remove-r-print-macro.md
index 43d2740..1aed5f7 100644
--- a/docs/dev/pages/issues/remove-r-print-macro.md
+++ b/docs/dev/pages/issues/_remove-r-print-macro.md
@@ -1,4 +1,8 @@
-<h1 align="center">Remove r_print! and r_println! Macros</h1>
+<h1 align="center">[Solved] Remove r_print! and r_println! Macros</h1>
+
+> [!NOTE]
+>
+> This issue has been fully resolved and is thus archived for preservation.
`r_print!` and `r_println!` are important macros in Mingling for use inside `#[help]` and `#[renderer]` functions, but their implementation is not clean: they implicitly introduce a `__renderer_inner_result` field. While this might look elegant at the API level, it is **incorrect** and even **objectionable**.
diff --git a/docs/dev/pages/issues/the-mod-pathfinder.md b/docs/dev/pages/issues/_the-mod-pathfinder.md
index 676251d..8869beb 100644
--- a/docs/dev/pages/issues/the-mod-pathfinder.md
+++ b/docs/dev/pages/issues/_the-mod-pathfinder.md
@@ -1,8 +1,12 @@
-<h1 align="center">The Mod Pathfinder</h1>
+<h1 align="center">[Solved] The Mod Pathfinder</h1>
<p align="center">
A build-time analyzer that computes full module paths for Mingling types, resolving path ambiguity in macros.
</p>
+> [!NOTE]
+>
+> This issue has been fully resolved and is thus archived for preservation.
+
## Background
Currently, `gen_program!` requires all involved types to be `use`d within their module. Mingling lacks a complete module path analyzer — waiting for `proc-macro-span` to stabilize is clearly not practical, so a solution for obtaining module paths is needed.