From 1c58eb0cabcdb114f710d0ffd6228c1f4d4ee99e Mon Sep 17 00:00:00 2001
From: Luthetus <45454132+huntercfreeman@users.noreply.github.com>
Date: Sun, 22 Dec 2024 22:16:26 -0500
Subject: [PATCH] Update IdeInfoDisplay.razor
---
.../Displays/Internals/IdeInfoDisplay.razor | 42 ++++++++++++++++++-
1 file changed, 41 insertions(+), 1 deletion(-)
diff --git a/Source/Lib/Ide/Ide.RazorLib/Shareds/Displays/Internals/IdeInfoDisplay.razor b/Source/Lib/Ide/Ide.RazorLib/Shareds/Displays/Internals/IdeInfoDisplay.razor
index a86ed5472..6723c3abe 100644
--- a/Source/Lib/Ide/Ide.RazorLib/Shareds/Displays/Internals/IdeInfoDisplay.razor
+++ b/Source/Lib/Ide/Ide.RazorLib/Shareds/Displays/Internals/IdeInfoDisplay.razor
@@ -172,8 +172,27 @@
Recent Changes:
-
v 0.9.7.12 (WIP_DATE)
+
v 0.9.7.12 (2024-12-22)
+ -
+ Show scope of lambda expression
+
+ -
+ Stop syntax highlighting member accesses as types erroneously.
+ (this turns off any syntax highlighting other than function invocation
+ but this turns out to be a massive quality of life improvement
+ while the types are being fully parsed).
+
+ -
+ DiscardSymbol (if '_' is a variable within scope it will be treated as
+ a variable otherwise it will be treated as 'discard').
+
+ -
+ Fix: is / is not pattern matching 'oldEvent is not RedundantTextEditorWork oldRedundantTextEditorWork' syntax.
+
+ -
+ Fix: 'out' syntax
+
-
FindOverlayDisplay fix bug if already open select then keybind wasn't populating
@@ -186,6 +205,27 @@
-
Identifiers as binary expression operands
+ -
+ Bind lambda expression variables within its scope (expression body, statement does not work).
+
+ -
+ SkipLambdaExpressionStatements(...) progress.
+ In short, I have a statement-loop, and inside of that is the expression-loop.
+
+ So, for Lambdas with statement-bodies, I need to go from the
+ statement-loop -> expression-loop -> statement-loop
+
+ All while not losing the state of any already existing loops. So it
+ seems a bit complicated. (the parser is written via primitive recursion with
+ a while loop, and I'd prefer to keep it that way.
+ This might have to be an exception though I'm not sure).
+
+ I want to focus on having the features that work... work
+ rather than having the lambda statements clobber features
+ that come after it (in a text file).
+
+ Lambda statements will be supported in the future though.
+