mirror of https://github.com/tbklang/tlang.git
Tristan B. Velloza Kildaire
c0920f2fdb
* Parser - Added a TODO in `parseReturn()` for issue #113 * Data - The `ReturnStmt` now has a default constructor which is for cases where one doesn't want to provide an expression (for expressionless returns) Parser - `parseReturn()` now supports expressionless returns Test cases - Added `simple_return_expressionless.t` to test expressionless return statement * Data - Added a method `hasReturnExpression()` to `ReturnStmt` which returns `true` if the return statement has an expression attached, `false` otherwise * Dependency - When processing a `ReturnStmt` only run do dependency generation for the return statement's expression IF it has one * Instruction - Made `ReturnInstruction` have a constructor which takes in no `Value` instruction (intended for return expression) - Added a `hasReturnExpInstr()` to `ReturnInstruction`such that during typechecking/codegen we can check for it * TypeChecker - Added a TODO regarding the missing typechecking for `ReturnStmt` typechecking. Added notes on how we'd go about this. - Fixed crash due to assuming there was always an expression on the stack that could be popped off for generating a `ReturnInstruction` (this is not the case when the return statement is expressionless) * Tests - Added a typecheck test for `simple_return_expressionless.t` * TypeChecker - Update `isSameType(Type t1, Type t2)` to check if the actual types of both `Type` objects are the same as a last resort - Added a `NOTE` comment on how `isSameType(Type t1, Type t2)` is implemented - Added typechecking code for `ReturnStmt` and updated the code generation with it. We now do the following: 1. We extract the container of the `ReturnStmt` and cast it to a `Function`; if it is not a `Function` we throw an error because you cannot have a `ReturnStmt` appear in a non-`Function` container 2. We extract the function's name relative to it container (the function's container) for use of it in error messages 3. Next, we get the return type of the function and do the following: a. If the return type is `void` i. If the return has an expression we throw an error ii. If the return has NO expression we pass typechecking and generate the `ReturnInstr` b. If the return type is non-`void` i. If the return has an expression we ensure that its type matches that of the function's return type and generate the `ReturnInstr` ii. If the return has NO expression we raise an exception as one is expected 4. If we pass and got here then we set the `ReturnInstr`'s context and `addInstrB(returnInstr)` * Test cases - Added test case `simple_return_type.t` which is here to test our return type checking * - Updated `.gitignore` * Parser - Use `lexer` for all `Token`-based operations |
||
|---|---|---|
| .. | ||
| d.yml | ||