You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Store references used in TS IdentiferReferences separately from normal references:
pubstructSymbolTable{pubresolved_references:IndexVec<SymbolId,Vec<ReferenceId>>,pubresolved_ts_references:IndexVec<SymbolId,Vec<ReferenceId>>,/* ... more ... */}
Advantage is that when transforming TS to JS, you can just clear resolved_ts_references (or ignore it) when calculating if a symbol is referenced or not.
Symbols would be stored together regardless of whether they're types or not to allow for when a symbol is used in both contexts e.g.:
The text was updated successfully, but these errors were encountered:
overlookmotel
changed the title
Store References for TS IdentiferReferences separately
Store References for TS IdentiferReferences separately in SemanticJun 6, 2024
overlookmotel
changed the title
Store References for TS IdentiferReferences separately in Semantic
Store References for TS identifers separately in SemanticJun 6, 2024
Boshen's idea from today's meeting:
Store references used in TS
IdentiferReference
s separately from normal references:Advantage is that when transforming TS to JS, you can just clear
resolved_ts_references
(or ignore it) when calculating if a symbol is referenced or not.Symbols would be stored together regardless of whether they're types or not to allow for when a symbol is used in both contexts e.g.:
Maybe use a different AST type
TSIdentiferReference
for identifiers in TS contexts, to simplify visitors.See also the point "Get rid of Reference" in #32.
The text was updated successfully, but these errors were encountered: