Type checking everything! #61

Open
opened 2022-12-17 15:38:26 +00:00 by deavmi · 3 comments
Owner

What is this?

Type checking is rather easy, for the most part, but it hasn't been the focus for the last few months. Rather code generation has. Therefore I want to track what parts of type checking are missing. Not all missing parts will be here, but we will have to manually check the code for missing ones before our alpha release. Form now on, however, I have decided to track the ones from here onwards.

Misc

Items that haven't been put in a category yet:

  • return statements are not yet type checked (related code gen topic #7)
    • ReturnStmt's expression is type checked and may only exist if non-void, and if void then no expression
    • Enforce that a return statement exists at the parser level
    • Enforce its placement as the last statement
  • if statements type checking (if that is even a thing?)

Arrays

Items relating to handling of arrays:

  • Array indexes (should only be integers) (see related topic #81)
  • Array assignments (see related topic #81)
# What is this? Type checking is rather easy, for the most part, but it hasn't been the focus for the last few months. Rather code generation has. Therefore I want to track what parts of type checking are missing. Not all missing parts will be here, but we will have to manually check the code for missing ones before our alpha release. Form now on, however, I have decided to track the ones from here onwards. ## Misc Items that haven't been put in a category yet: - [x] `return` statements are not yet type checked (related code gen topic #7) - [x] `ReturnStmt`'s expression is type checked and may only exist if non-void, and if void then no expression - [ ] Enforce that a return statement exists at the parser level - [ ] Enforce its placement as the last statement - [ ] `if` statements type checking (if that is even a thing?) ## Arrays Items relating to handling of arrays: - [ ] Array indexes (should only be integers) (see related topic #81) - [ ] Array assignments (see related topic #81)
deavmi added the
typing
label 2022-12-17 15:39:27 +00:00
deavmi added this to the Dependency tree, type-checking and codegen project 2022-12-17 15:39:37 +00:00
deavmi changed title from Type checking to Type checking everything! 2022-12-17 15:39:46 +00:00
deavmi added the due date 2023-02-14 2022-12-17 15:39:59 +00:00
deavmi self-assigned this 2022-12-19 13:42:02 +00:00
deavmi added reference vardec_varass_dependency 2023-03-08 14:01:45 +00:00
deavmi added this to the Basics milestone 2023-03-08 14:02:08 +00:00
Author
Owner

This depends on #115 as that is the new mechanism that will be used.

This depends on #115 as that is the new mechanism that will be used.
deavmi added a new dependency 2023-07-09 14:18:35 +01:00
deavmi modified the due date from 2023-02-14 to 2023-08-06 2023-07-09 14:24:41 +01:00
deavmi started working 2023-07-13 12:36:54 +01:00
Author
Owner

Changing branch to feature/universal_coercion as that is where all the type checking is happening

Changing branch to `feature/universal_coercion` as that is where all the type checking is happening
deavmi changed reference from vardec_varass_dependency to feature/universal_coercion 2023-07-13 12:37:52 +01:00
Author
Owner

What is this?

Type checking is rather easy, for the most part, but it hasn't been the focus for the last few months. Rather code generation has. Therefore I want to track what parts of type checking are missing. Not all missing parts will be here, but we will have to manually check the code for missing ones before our alpha release. Form now on, however, I have decided to track the ones from here onwards.

Misc

Items that haven't been put in a category yet:

  • return statements are not yet type checked (related code gen topic #7)
  • if statements type checking (if that is even a thing?)

Arrays

Items relating to handling of arrays:

  • Array indexes (should only be integers) (see related topic #81)
  • Array assignments (see related topic #81)

return statements now checked as of #113

> # What is this? > > Type checking is rather easy, for the most part, but it hasn't been the focus for the last few months. Rather code generation has. Therefore I want to track what parts of type checking are missing. Not all missing parts will be here, but we will have to manually check the code for missing ones before our alpha release. Form now on, however, I have decided to track the ones from here onwards. > > ## Misc > > Items that haven't been put in a category yet: > > - [x] `return` statements are not yet type checked (related code gen topic #7) > - [ ] `if` statements type checking (if that is even a thing?) > > ## Arrays > > Items relating to handling of arrays: > > > - [ ] Array indexes (should only be integers) (see related topic #81) > - [ ] Array assignments (see related topic #81) `return` statements now checked as of #113
deavmi stopped working 2023-07-13 12:38:32 +01:00
1 minute 38 seconds
deavmi added the
parser
label 2023-07-13 12:42:39 +01:00
deavmi started working 2023-07-13 12:43:17 +01:00
deavmi stopped working 2023-07-13 12:43:22 +01:00
5 seconds
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
Notifications
Total Time Spent: 1 minute 43 seconds
deavmi
1 minute 43 seconds
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

2023-08-06

Reference: tlang/tlang#61
No description provided.