From 5f64d70fbb607825e50d9f2763d889d90a08da45 Mon Sep 17 00:00:00 2001
From: "Alex A. Naanou" <alex.nanou@gmail.com>
Date: Mon, 6 Jul 2026 00:02:04 +0300
Subject: [PATCH] cleanup + notes...

Signed-off-by: Alex A. Naanou <alex.nanou@gmail.com>
---
 v3/pwiki/parser.js | 22 +++-------------------
 1 file changed, 3 insertions(+), 19 deletions(-)

diff --git a/v3/pwiki/parser.js b/v3/pwiki/parser.js
index 6f32485..140ba80 100644
--- a/v3/pwiki/parser.js
+++ b/v3/pwiki/parser.js
@@ -742,25 +742,9 @@ module.BaseParser = {
 	// 		times...
 	//
 	//
-	// XXX these yeild different results:
-	// 			r = parser.resolve(
-	// 				tests.P, 
-	// 				'<slot X>@include(/async/page)</slot> <slot X value>',
-	// 				s = {})
-	// 			s.wait.then(function(){
-	// 				console.log(r) }) // -> ['Page '] (err)
-	// 		and:
-	// 			r = parser.expand(
-	// 				tests.P, 
-	// 				'<slot X>@include(/async/page)</slot> <slot X slot/>',
-	// 				s = {})
-	// 			s.wait.then(function(){
-	// 				r = parser.resolve(test.P, r, s)
-	// 				console.log(r) }) // -> ['slot '] (correct)
-	// 		-> promises seem to not be sequenced correctly here...
-	// 		XXX it looks like the first slot is resolved before the last 
-	// 			slot has a chance to set the value as it is waiting for 
-	// 			the first slot to finish...
+	// XXX can we prevent reaces over state.unresolved???
+	// 		it can be deleted when calling .parse(..) / .parseNested(..)
+	// 		while parsing, for example from within a macro...
 	resolve: function(page, ast, state={}, nested_handlers={}){
 		var that = this
 		ast = typeof(ast) != 'object' ?