1. 13
  1. 7

    Confirmed: Rob Pike reads Eli’s blog. https://github.com/golang/go/issues/53261

    1. 3

      Quite possible, though it’s equally likely he saw the related Go change that Eli submitted: https://go-review.googlesource.com/c/go/+/410296

      1. 1

        Confirmed: Rob Pike reads Eli’s blog

        Respectfully: why does this matter?

        1. 2

          Matter in what sense? It’s just amusing that Eli posted a blog entry about improving performance and then the Go team member responsible posted an issue proposing to do the same thing. The issue doesn’t mention the blog post, but the timing is too close for it to be coincidence. Alas, Ben Hoyt thinks the issue was in response to a change request, and not the blog per se.

      2. 1

        Pull-based concurrency for the win. Note that Rust’s futures (and unstable generators) are pull-based, rather than (the more common) push-based.