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

Add first-class stack safety #78

Open
sbuzzard opened this issue May 11, 2019 · 0 comments
Open

Add first-class stack safety #78

sbuzzard opened this issue May 11, 2019 · 0 comments
Assignees

Comments

@sbuzzard
Copy link
Member

Currently dtrace leans on it's underlying effect for stack safety, which works ok for effects like IO that provide it but even IO is inadequate for dtrace needs as even for map/ap operations, we need that suspension because of our Kleisli-like nature (with the TC => F[?] that represents a span). So we use a bunch of hacks which generally "work" but only with a bunch of implicit constraints. I labeled this an enhancement but its really fixing an underlying design flaw.

@sbuzzard sbuzzard self-assigned this May 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant