LiftTrace concept
#448
Closed
LiftTrace concept
#448
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Yeah, just ignore everything above, I bungled it 😅 obviously the problem with an opaque effect is that you don't have any other constraints available besides |
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
So this is not quite what we discussed on Discord, but I hope you'll like it better since you are suspicious of the two-parameter typeclasses. This does away with that by keeping the effect used for tracing completely opaque. This enables instances for bothKleisliandIOLocal.IMO the ugliest part of it is that users will have to wrap their program in:Everything subject to bikeshed of course. Let me know what you think!