Should the optionality of the annotation be part of the generic type? Right now, every annotation is optional (even when a type like () is chosen), which seems undesirable. If the user of the API had to specific an optional annotation type when an optional annotation was desired, it would save space for users who use no annotations and improve the API for users who require every term be annotated.
Should the optionality of the annotation be part of the generic type? Right now, every annotation is optional (even when a type like
()is chosen), which seems undesirable. If the user of the API had to specific an optional annotation type when an optional annotation was desired, it would save space for users who use no annotations and improve the API for users who require every term be annotated.