2 ms·

Note that this is being fixed in the next release: https://golang.org/issue/10958 https://golang.org/issue/10958

• littlestymaar 7y ago
  That's cool it's finally coming, this issue is open since 2015! I wonder which performance impact this will have.