You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Export symbols are of the form _export{compartment name}_{mangled symbol name}. If we fail to resolve one of these, it would be nice to see if any of the input files has a private symbol that matches {mangled symbol name} and provide a diagnostic. This can happen if you have failed to mark a function with the __cher_compartment macro in the definition, but you did in a declaration that was visible to the caller.
The text was updated successfully, but these errors were encountered:
I think I see the issue now. The diagnostic will warn in the case where you have a correctly annotated implementation and an incorrectly annotated caller. You're looking for the inverse case, with an incorrectly annotated implementation and a correctly annotated caller.
Export symbols are of the form _export{compartment name}_{mangled symbol name}. If we fail to resolve one of these, it would be nice to see if any of the input files has a private symbol that matches {mangled symbol name} and provide a diagnostic. This can happen if you have failed to mark a function with the
__cher_compartment
macro in the definition, but you did in a declaration that was visible to the caller.The text was updated successfully, but these errors were encountered: