This repository has been archived by the owner on Sep 7, 2023. It is now read-only.

Full handling for type name hierarchy #58

Closed

6 tasks done

jeromesimeon opened this issue Apr 13, 2018 · 1 comment

Assignees

Labels

Category: Backend Range: Semantics Range: Typing Type: Bug 🐛

Member

jeromesimeon commented Apr 13, 2018 •

edited

Loading

Type name hierarchy is not yet handled properly. This is relevant for code generation, the reference interpreter, and of course for type checking.

Requires some of the following steps:

Import of CTO files (See CTO Import #9)
Namespace resolution (See Namespace handling #18)
Uniform handling of CTOs and type declaration in module (done in PR (feature) Finish translation of CTO as Ergo modules #234)
Extract type hierarchy from ergo modules after namespace resolution (See Extract type name hierarchy from declared CTO #330)
Pass type hierarchy to backend compiler calls
Add code-generation for type hierarchy

jeromesimeon added Type: Bug 🐛 Category: Backend Range: Typing labels

jeromesimeon self-assigned this

jeromesimeon changed the title ~~Export type inheritance hierarchy in JavaScript backend~~ Full handling for type name hierarchy

jeromesimeon added the Range: Semantics label

jeromesimeon mentioned this issue

Extract type name hierarchy from declared CTO #330

Closed

Member Author

jeromesimeon commented Jan 8, 2019

Finally fixed in PR #501

jeromesimeon closed this as completed

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.