Generalizing PrintRead to allow type information to change the generated builtin.
#155
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR changes
to
s.t. the generated
qvnmay be influenced by the types it is instantiated with.This is important because in languages without type classes, we need to explicitly say which instance should be used. For example if we have type
when we generate the Eq instance, writing something like
won't suffice, as we must provide the type information of
IntandChartoa0 `eq` a1andb0 `eq` b1respectively. We would need to write something likeAdmittedly, I see this as a temporary fix since the builtins really should provide the types they may be instantiated with e.g. we shouldn't just have
eqas a builtin -- we should haveeqinstantiated with typesInt,Char, blah blah blah, are all builtins