Writing (and debugging) the async logic in the bjam C code is extremely painful.
With Python (3)'s async support, writing similar workflows is expected to be much simpler. In addition, this would open the door to another of other improvements (debuggability, tracability, etc.).
Writing (and debugging) the async logic in the
bjam
C code is extremely painful. With Python (3)'s async support, writing similar workflows is expected to be much simpler. In addition, this would open the door to another of other improvements (debuggability, tracability, etc.).