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
{{ message }}
This repository has been archived by the owner on Oct 2, 2020. It is now read-only.
Failed to reconstruct: #<File src/worldsingles/payment/sbw.clj>
Internal Error (slamhound.sandbox__1222__auto__:<NO LINE>) Cannot resolve type: Vec
Hint: Is Vec in scope?
Hint: Has Vec's annotation been found via check-ns, cf or typed-deps?
Note, as with the previous core.typed / Slamhound issue, it tries to run core.typed after failing to reconstruct the namespace (the Internal Error is from core.typed). Slamhound doesn't explain why it can't reconstruct the namespace.
The text was updated successfully, but these errors were encountered:
Both of these issues appear to stem from the fact that in an effort to provide user friendly messages, core.typed macros catch the Exceptions that Slamhound uses to identify unknown references.
ATM I think we will probably need to add explicit support for core.typed (since it is a contrib library). In the long term I hope to move Slamhound to use the new static analyzers; if this is possible this kind of workaround won't be necessary.
We refer certain type aliases in from core.typed:
Then we have create a type alias:
Slamhound barfs on the use of
Vec
:Note, as with the previous core.typed / Slamhound issue, it tries to run core.typed after failing to reconstruct the namespace (the Internal Error is from core.typed). Slamhound doesn't explain why it can't reconstruct the namespace.
The text was updated successfully, but these errors were encountered: