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
Kind and TypeVariableKind currently have different behavior for the same name (Normal) and because of it, Type::kind() -> Option<Kind> currently ignores TypeVariableKind info.
Happy Case
Match kinds between TypeVariableKind and Kind
Make TypeVariableKind::Normal correspond to Kind::Normal or else rename to avoid confusion
This may require adding some sort of Kind::Any/Kind::Unresolved or propagating a lot more Kind information, e.g. in the generics in Type::Forall
This will allow removing None as an "any" kind in Type::kind
Use the matched kinds to allow Type::kind() on type variables to account for the TypeVariableKind
Add tests to ensure moving between types that use Kind (e.g. Type::Constant) and type variables preserves the kind
Workaround
None
Workaround Description
No response
Additional Context
No response
Project Impact
None
Blocker Context
No response
Would you like to submit a PR for this Issue?
None
Support Needs
No response
The text was updated successfully, but these errors were encountered:
# Description
## Problem\*
Resolves#6067
## Summary\*
- Combines `TypeVariableKind` and `Kind` (now only `Kind`)
- Adds `Kind` arguments where needed
- Adds more `Kind` checks
## Additional Context
## Documentation\*
Check one:
- [x] No documentation needed.
- [ ] Documentation included in this PR.
- [ ] **[For Experimental Features]** Documentation to be submitted in a
separate PR.
# PR Checklist\*
- [x] I have tested the changes locally.
- [x] I have formatted the changes with [Prettier](https://prettier.io/)
and/or `cargo fmt` on default settings.
---------
Co-authored-by: Tom French <15848336+TomAFrench@users.noreply.github.com>
Co-authored-by: Maxim Vezenov <mvezenov@gmail.com>
Problem
Kind
andTypeVariableKind
currently have different behavior for the same name (Normal
) and because of it,Type::kind() -> Option<Kind>
currently ignoresTypeVariableKind
info.Happy Case
TypeVariableKind
andKind
TypeVariableKind::Normal
correspond toKind::Normal
or else rename to avoid confusionKind::Any
/Kind::Unresolved
or propagating a lot moreKind
information, e.g. in the generics inType::Forall
None
as an "any" kind inType::kind
Type::kind()
on type variables to account for theTypeVariableKind
Kind
(e.g.Type::Constant
) and type variables preserves the kindWorkaround
None
Workaround Description
No response
Additional Context
No response
Project Impact
None
Blocker Context
No response
Would you like to submit a PR for this Issue?
None
Support Needs
No response
The text was updated successfully, but these errors were encountered: