Jean Boussier

> Many callcaches tend to be allocated after boot as there's no good way (yet?) to warm them up. Ah my bad, I'm much less familiar with this part of...

IMO this change is justified simply by readability. `bool * RUBY_Qtrue` is a nice hack but is absolutely not obvious. I don't see any argument not to change it.

I think It's more `proc{}` you'd want to benchmark

Sure. But note that I'm not the maintainer, I can't merge your changes. https://github.com/ruby/ruby/blob/master/doc/maintainers.md#libnethttprb-libnethttpsrb

It also showcase all the problems with streaming: - Reverse-Proxy buffering - Can no longer changes headers - Can no long change status code - Implementation complexity 103 Early Hints...

> And yet the conclusion appears at face value to be strongly in favour of streaming I don't get what makes you say that. The article never mention early hints,...

> Early hints create extra network overhead. It's extremely negligible. Still don't understand where you see a roundtrip.... >> You can emit as many 103 responses as you want, as...

> Early Hints only has any potential benefit on the first request before any cache is established for a site. It's the same problem as push promises, which have effectively...

@fatkodima no it should be unrelated.

You should start by rebasing on my PR, you'd have the new functions lined up etc.