Type resolution notes #1

Open
opened 1 year ago by deavmi · 0 comments
deavmi commented 1 year ago
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 1 year ago
deavmi added the typing label 1 year ago
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date

No due date set.

Dependencies

No dependencies set.

Reference: tlang/tlang#1
Loading…
There is no content yet.