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 need a way of converting Quoted token streams into trait constraints when quoted values are given as arguments to annotations.
Happy Case
We should add a Quoted::as_trait_constraint conversion method.
For now we can error if it cannot be converted to a trait constraint. In the future we may likely want to return a Option<TraitConstraint> instead. This lets the user continue if it was not a valid trait constraint, but the error message they can give will be less specific than the one we can give in the compiler.
Project Impact
None
Impact Context
No response
Workaround
None
Workaround Description
No response
Additional 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#5480Resolves#5481
## Summary\*
Adds:
- The `TraitConstraint` type
- `impl Eq for TraitConstraint`
- `impl Hash for TraitConstraint`
- `Quoted::as_trait_constraint`
## Additional Context
Ran into the type error when calling trait impls issue again while
working on this. Hence why it is a draft.
## Documentation\*
Check one:
- [ ] No documentation needed.
- [ ] Documentation included in this PR.
- [x] **[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.
Problem
We need a way of converting
Quoted
token streams into trait constraints when quoted values are given as arguments to annotations.Happy Case
We should add a
Quoted::as_trait_constraint
conversion method.For now we can error if it cannot be converted to a trait constraint. In the future we may likely want to return a
Option<TraitConstraint>
instead. This lets the user continue if it was not a valid trait constraint, but the error message they can give will be less specific than the one we can give in the compiler.Project Impact
None
Impact Context
No response
Workaround
None
Workaround Description
No response
Additional 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: