Closed DamDC91 closed 2 years ago
Hello @DamDC91,
Thank you for reporting this issue. We are working on a fix.
Best regards,
Hello again,
This error was due to a defficiency of our heuristic to compute precise types from parsing rules. It is now fixed, thank you again for reporting this.
Hello,
I’m working on an open source LangKit plugin to export LibAdaLang analysis in Rascal.
Some of my plugin logic is based on the
precise_types
property of the LangKit classField
. This property is supposed to return the precise set of types that this field can contain. However, sometimes this property gives an irrelevant output. In other words, some LibadalangF_...
functions don’t have documentation on which type can be returned.The following functions/fields are the ones that are problematic for me:
Calling
precise_types
on these fields gives me all the types (not very precise).I think improving the documentation of LibAdaLang will benefit every user in addition to help me.
Thanks for your help.
Damien