Arrow 3 when?!??!?
#3817
Replies: 4 comments 1 reply
|
The easiest thing to mention is any deprecated hidden functions that were there only for binary compatibility |
1 reply
|
In addition, there's some old |
|
I think we must wait at the very least for context parameters to be out and stable. |
0 replies
|
This might be a bad idea, but unifying the Ior and Either hierarchies might be interesting. It's as simple as having |
0 replies
|
As far as the previous plans go, the only potential breaking change is dropping extension-based DSLs in favor of context-parameter-based ones. But as you say, we'd need for context parameters to be stable. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Collecting thoughts here about when should Arrow 3 become a thing, and what breaking changes should it include.
Ideally, we want most changes to be done directly to Arrow 2, using deprecations, to help smooth the process. Some things might be better done in a big update, though.
All reactions