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

Try using info() instead of type(). #18

Merged
merged 3 commits into from
Sep 26, 2012

Conversation

johntyree
Copy link
Contributor

It's hard to say if this is a better approach or not, but at least it does the typeclass constraints properly.

@johntyree
Copy link
Contributor Author

Ok, now it uses info() if we're planning on inserting the type into column 1 (top-level), otherwise fall back to using type() and the user will just have to put in typeclass constraints as necessary.

@johntyree
Copy link
Contributor Author

Don't pull this yet. We could still fall back to type() when info() fails due to ambiguity, for example.

Fall back to using `type()` if `info()` doesn't work for some reason. For
example if the identifier is ambiguous or we aren't top-level.
@johntyree
Copy link
Contributor Author

This works well I think. The only two remaining issues I see are that the "modified buffer" error prints twice due to the two calls, and that we could try to resolve the ambiguity problem by calling info() on the qualified symbol name using detect_module().

eagletmt added a commit that referenced this pull request Sep 26, 2012
Try using info() instead of type().
@eagletmt eagletmt merged commit 005fd8e into eagletmt:master Sep 26, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants