-
Notifications
You must be signed in to change notification settings - Fork 374
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consider adding value AnnotationAccessors #2403
Comments
AnnotationId<TValue> looks similar to HttpRequestOptionsKey<TValue>. And now I realize it has already been implemented and just doesn't show up in GitHub code search because that doesn't cover non-default branches. |
|
Value annotation accessors would do two things:
And example is default values which are stored as
object?
While it would be nice to store the specific value, rather than the general one, I do not see a way that is possible. However, I think the code below would solve the two problems above:
If we wish this to be polymorphic with other AnnotationAccessors, it could derive from it, in which case it could also drop
SetAnnotation
The text was updated successfully, but these errors were encountered: