Consider this code:
typedef struct { int x; int y; } Point
This generates two classes:
* Point$0 (the anonymous struct)
* Point (a typedef to the anonymous struct)
While this is technically correct, this idiom is so common that we should just emit a single struct class. In fact, this was already the case before we tweaked the jextract implementation.
typedef struct { int x; int y; } Point
This generates two classes:
* Point$0 (the anonymous struct)
* Point (a typedef to the anonymous struct)
While this is technically correct, this idiom is so common that we should just emit a single struct class. In fact, this was already the case before we tweaked the jextract implementation.
- relates to
-
CODETOOLS-7903647 typedef of function pointers generates a redundant class
-
- Resolved
-
