scip-code/scip/issues/154 added support for a number of new fields in SCIP's SymbolInformation:
kind
display_name
signature_documentation
enclosing_symbol (what was originally proposed as owner or parent in the linked issue)
On the Java side the sematicdb data already contains the kind (and properties, eg to build an AbstractMethod), but it does not on the Kotlin side.
For both Java and Kotlin:
scip-code/scip/issues/154 added support for a number of new fields in SCIP's
SymbolInformation:kinddisplay_namesignature_documentationenclosing_symbol(what was originally proposed asownerorparentin the linked issue)On the Java side the sematicdb data already contains the kind (and properties, eg to build an AbstractMethod), but it does not on the Kotlin side.
For both Java and Kotlin: