proc: Removed setChanRecvBreakpoints
This function was broken for a very long time until the changes in this PR fixed it. However I do not think it is desirable to be catapulted into some other goroutine by 'next' just because that other goroutine happened to receive a message on a channel. This feature should be implemented by a new command, not next.
Showing
想要评论请 注册 或 登录