-
Notifications
You must be signed in to change notification settings - Fork 140
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
Copy symbolic errors when composing #333
Conversation
e660060
to
098e4c6
Compare
Another one for you to review, @AaronLasseigne. This suffers from the same problems mentioned in #194 (comment), but I think the tradeoffs are worth it. I think #245 could provide a better long-term solution for this. I don't want to let perfect be the enemy of good, though. |
It looks good and what we currently do is (as you pointed out) not very good. I think we just need to mention some of these sharp edges in the docs. |
Should I add that to the "Errors" section or the "Composition" section? |
Probably the "Errors" section and then link to it from the "Composition" section. Does that sound reasonable? |
👍 |
b10c1dc
to
b804eba
Compare
I updated the documentation. |
This is a breaking change, so it'll need to be merged into a branch for v3.0.0. |
True. |
Copy symbolic errors when composing
Fixes #87.