From f5c8f6fa626d05c9615f606c03b28dc9a74847a7 Mon Sep 17 00:00:00 2001 From: LordBaryhobal Date: Wed, 13 May 2026 11:15:40 +0200 Subject: [PATCH] fix(research): typo in syntax brainstorming --- research/01_syntax.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/research/01_syntax.md b/research/01_syntax.md index 286d989..1902e90 100644 --- a/research/01_syntax.md +++ b/research/01_syntax.md @@ -1,6 +1,6 @@ # Syntax Brainstorming -The syntax depends on the kind of implementation. For example, we could want the type system to be valid Python and use Python classes, functions and annotations. In that case, the syntax would be quite restricted by the available set of valid Python expression which don't affect have a direct effect on the program. +The syntax depends on the kind of implementation. For example, we could want the type system to be valid Python and use Python classes, functions and annotations. In that case, the syntax would be quite restricted by the available set of valid Python expression which don't have a direct effect on the program. Moreover, if we do use Python's builtin syntax, there could be two approaches: either define real Python classes and functions in Python, or simply use the syntax and parse it externally, without any real Python semantic. @@ -24,7 +24,7 @@ In terms of integration, the first option seems the most well suited as it provi - Can be quite verbose - Doesn't involve the creation of a custom parser -Looking at the following examples, my personnal preference would go towards the last option. The only notable downsides with that option is the need to compile the code to make it become valid Python, and the fact that it doesn't integrate into any Python LSP as is. +Looking at the following examples, my personal preference would go towards the last option. The only notable downsides with that option is the need to compile the code to make it become valid Python, and the fact that it doesn't integrate into any Python LSP as is. ## Required syntax elements