PolymorphicQualifier for qualifiers with elements (values, fields)

[GoogleCodeExporter]

Currently, checkers.quals.PolymorphicQualifier does not support an
annotation value.

In contrast, checkers.igj.quals.I supports a String to distinguish
different uses of the polymorphic qualifier.

Adding a String value to PolymorphicQualifier would give the same
expressiveness to the type systems using it, e.g. PolyNull.

Original issue reported on code.google.com by [email protected] on 16 Feb 2010 at 1:43

[GoogleCodeExporter]

This is a generalization of issue 54.  (And is the right way to solve issue 54.)

Original comment by [email protected] on 16 Feb 2010 at 3:38

• Added labels: Priority-Medium
• Removed labels: Priority-Low

[GoogleCodeExporter]

Can you explain the proposal again please?  PolymorphicQualifier is 
meta-annotation on the annotation 
declaration, so programmers shouldn't use it directly.

Providing an example of how it might work in practice would help our 
understanding.

Original comment by [email protected] on 26 Feb 2010 at 10:33

[GoogleCodeExporter]

@PolymorphicQualifier should not take an argument.  (So the text about "Adding a
String value to PolymorphicQualifier" in the original request is a bit 
misleading .)

Rather, the proposal is that every qualifier marked as @PolymorphicQualifier 
should
take an optional argument, and the Checker Framework should respect the argument
while doing checking.

After this enhancement, then it would be possible to meta-annotate @I as
@PolymorphicQualifier.  All handling for the argument to @I could be moved out 
of the
IGJ checker and into the framework proper, where other checkers could take 
advantage
if it for free.

Original comment by [email protected] on 27 Feb 2010 at 12:10

[GoogleCodeExporter]

Issue 54 has been merged into this issue.

Original comment by [email protected] on 3 Mar 2010 at 10:37

[GoogleCodeExporter]

Original comment by [email protected] on 26 Jan 2011 at 9:52

• Added labels: Priority-Low
• Removed labels: Priority-Medium

[mernst]

This issue was fixed quite a while ago.