Organize generic arguments as layouts #415
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A brainstorming PR to see what it looks like to organize various walls of generic parameters behind types that provide coherent associated type guidance. Many type signatures and
where
clause lengths decrease. The main downside is that I struggled to maintain the constraint thatO
must have itsTryInto::Err
variants implementDebug
. I didn't try too hard, but all that is lost is naming a specific number that cannot be cast should it error (it shouldn't!).There is still all ofI thought I'd put this up to look at it.OrdKey*
to do, butcc: @antiguru, @petrosagg