Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

respect opaqueness of @opaque types #43

Open
msz opened this issue May 30, 2020 · 0 comments
Open

respect opaqueness of @opaque types #43

msz opened this issue May 30, 2020 · 0 comments
Labels
enhancement New feature or request

Comments

@msz
Copy link
Owner

msz commented May 30, 2020

Right now Hammox is treating @opaque just like a public type, which means if matching fails it will show a stacktrace going into the internals of the type. We should modify this so that the stacktrace stops at the opaque type.

msz added a commit that referenced this issue May 30, 2020
Fixes #41.

Hammox blows up when encountering `@typep` and `@opaque`. For now we
will treat them like any other type.

Further work on opaque types in #43.
@msz msz added the enhancement New feature or request label May 30, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant