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
We can probably use a similar technique to what we did with the struct definitions: Add a literal variant "Unresolved" which must then be matched with the content of the associated constant declarations an appropriate place in the compiler pipeline, probably in types.rs where we are doing this match for structs.
Just like DataType has a method for resolve_type that takes the declared structs and maps any unresolved type to one of those, so too could resolve_literal map unresolved literals to those from a constant list stored in the type checkers CheckState struct.
The text was updated successfully, but these errors were encountered:
Goal: To be allowed to write this
instead of that:
We can probably use a similar technique to what we did with the struct definitions: Add a literal variant "Unresolved" which must then be matched with the content of the associated constant declarations an appropriate place in the compiler pipeline, probably in
types.rs
where we are doing this match for structs.Just like
DataType
has a method forresolve_type
that takes the declared structs and maps any unresolved type to one of those, so too couldresolve_literal
map unresolved literals to those from a constant list stored in the type checkersCheckState
struct.The text was updated successfully, but these errors were encountered: