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.

Sign up for GitHub

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

Jump to bottom

initial type for inference -- not found should be more clearly differentiated from other error types #269

Open

baroquebobcat opened this issue Oct 14, 2014 · 0 comments

Member

baroquebobcat commented Oct 14, 2014

maybe have a separate subclass. This makes it hard to see different kinds of errors when using verbose logging.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment