Type resolution notes #1

Open
opened 2022-07-30 11:06:55 +01:00 by deavmi · 0 comments
Owner

Currently we resolve types in the following order, which for the addition of container types such as <UserDefinedType>* would probably fail as of the order
we do this in.

Resolution order

  1. getBuiltInType()
    • Only chop-and-recurse for <type>*
    • That should actually capture user defined types me thinks? - yeah
  2. On failure of getBuiltInType() resolve by entity lookup
Currently we resolve types in the following order, which for the addition of container types such as `<UserDefinedType>*` would probably fail as of the order we do this in. ![](http://deavmi.assigned.network/git/attachments/8e59920a-72ee-4945-af1d-a2d2e79fc610type_res.png) ### Resolution order 1. `getBuiltInType()` * Only chop-and-recurse for `<type>*` * That should actually capture user defined types me thinks? - yeah 2. On failure of `getBuiltInType()` resolve by entity lookup
deavmi self-assigned this 2022-07-30 11:18:15 +01:00
deavmi added the
typing
label 2022-07-30 11:19:25 +01:00
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: tlang/tlang#1
No description provided.