Comment by ximeng

I complained about the communications around this issue a few weeks ago, and bcherny popped up in the comments with an explanation of what they were doing. Now there’s a fix with a great explanation of the background to this bug and future directions from chrislloyd.