Skip to content

Fix the optional type name and type identifier resolution#870

Merged
TristonianJones merged 1 commit intogoogle:masterfrom
TristonianJones:optional-type-fix
Jan 7, 2024
Merged

Fix the optional type name and type identifier resolution#870
TristonianJones merged 1 commit intogoogle:masterfrom
TristonianJones:optional-type-fix

Conversation

@TristonianJones
Copy link
Collaborator

When calling type(<optional>) the expected output would be optional; however, this fails
since the name optional is part of the namespace. To ensure optionals are type-testable,
the type name has been shifted to optional_type. This should not break anyone unless you
are explicitly querying the type name as part of your implementation.

Additionally, this fix revealed a different issue wherein type identifiers were not being resolved
during type-check unless they were for structured object types. This change introduces a call
to FindIdent which is also the same call being made at runtime to resolve type identifiers
during evaluation.

@TristonianJones TristonianJones merged commit d45f67f into google:master Jan 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants