From a0baa3f8b4c67d79977b53cf29ae26b44b6372a9 Mon Sep 17 00:00:00 2001 From: Brendan Hansen Date: Sun, 21 Nov 2021 21:28:51 -0600 Subject: [PATCH] tiny notes --- src/checker.c | 1 + src/polymorph.c | 2 +- 2 files changed, 2 insertions(+), 1 deletion(-) diff --git a/src/checker.c b/src/checker.c index 0a68c9a6..1dec37d7 100644 --- a/src/checker.c +++ b/src/checker.c @@ -737,6 +737,7 @@ CheckStatus check_binaryop_assignment(AstBinaryOp** pbinop) { } else { // NOTE: +=, -=, ... + // NOTE: At this point, it is assumed that operator overloads for +=, -=, etc have been tested. BinaryOp operation = -1; if (binop->operation == Binary_Op_Assign_Add) operation = Binary_Op_Add; diff --git a/src/polymorph.c b/src/polymorph.c index 8c5d237f..55302c19 100644 --- a/src/polymorph.c +++ b/src/polymorph.c @@ -505,7 +505,7 @@ static void solve_for_polymorphic_param_type(PolySolveResult* resolved, AstFunct // NOTE: The job of this function is to look through the arguments provided and find a matching // value that is to be baked into the polymorphic procedures poly-scope. It expected that param -// will be of kind PPK_Baked_Value. +// will be of kind PPK_Baked_Value. In other words, this handles the ($Baked: type) case. // CLEANUP: This function is kind of gross at the moment, because it handles different cases for // the argument kind. When type expressions (type_expr) become first-class types in the type // system, this code should be able to be a lot cleaner. -- 2.25.1