Add basic handling for generics in derive macro #41
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.
This is pretty simple, I've tried to do the bare minimum to get things working, rather than make things too complex, but it solves my initial use-case, and making future changes with generics should be a simple additive process when new use-cases are found.
We basically pull the type params out of the generics object (i.e. not the lifetimes, and not any const parameters either), and, if there are any, create a
where
-clause ofT: ::ramhorns::Content
for each type param (i.e.T
) that has been declared.There are probably improvements that could be made, such as not adding the type bound if the
ramhorns(skip)
attribute is used for that field, or copying over other type bounds that exist, but I figure they can be added later if they are likely to actually be useful to someone.Closes #38