From 023dd05267d61ffeddf514bf1af46d9b129bbe67 Mon Sep 17 00:00:00 2001 From: Tom Alexander Date: Thu, 10 Aug 2023 18:52:02 -0400 Subject: [PATCH] Remove outdated notes. --- notes/exit_matcher_loop_notes.txt | 35 ------------------------------- 1 file changed, 35 deletions(-) delete mode 100644 notes/exit_matcher_loop_notes.txt diff --git a/notes/exit_matcher_loop_notes.txt b/notes/exit_matcher_loop_notes.txt deleted file mode 100644 index 5e357ae7..00000000 --- a/notes/exit_matcher_loop_notes.txt +++ /dev/null @@ -1,35 +0,0 @@ -Headings add exit matcher for heading - -Paragraphs add exit matcher for elements (but it should be sans paragraph) - - - - -* foo -* bar -* baz - -context tree -> () - -match * foo - -context tree -> exit(heading matcher) - -check exit -invoke heading matcher -check exit -invoke heading matcher -check exit -invoke heading matcher -adds second heading matcher exit - - -Ways around this: -- Always parse SOMETHING before checking for exit - - Doesn't always seem possible -- Disable exit matchers during exit check - - Seems like it would break syntax -- Have separate parsers for the beginning of the exit condition (for example, checking for just the headline instead of the full heading parser) - - Won't be possible with paragraphs ending at any other element -- Check exit matchers in parent parser - - Will this work? seems like it would just create larger loops