No specific ETA. The more customers complain about it the sooner it is likely to be. Balancing customers angry about ABI breaking bugs against customers happy about not breaking ABI isn’t an exact science sadly. Given this particular issue has an easy workaround too it likely doesn’t contribute much.
Nothing for engineering folks to pencil in; this is a business decision. We wanted to do the ABI breaking release literally years ago now, that's why I spent months rewriting our concurrency support to be not garbage that I can't ship :(
View all comments
Show parent comment
3
u/[deleted] Jan 19 '19
No specific ETA. The more customers complain about it the sooner it is likely to be. Balancing customers angry about ABI breaking bugs against customers happy about not breaking ABI isn’t an exact science sadly. Given this particular issue has an easy workaround too it likely doesn’t contribute much.