Evan Phoenix
Evan Phoenix
No, we should not do this. The JIT'd code will never be as fast as the current code and we get nothing expect new bugs from doing it.
If someone can show a pure-ruby http parser that only adds 1ms to requests I'll certainly entertain the idea.
@nateberkopec I've added a take at auto warmup using a fairly simple (but stable) approach.
What advantage would there be to rewriting it in Rust?
Anything we can do to help get this merged? Would love to see it land.
Hi @Mossaka, Thanks for opening this. My personal preference is the sealed interface. I see in the original issue some concern about allocations related to passing back ints, but unless...
Looking at the proposals again, I'd agree with @johanbrandhorst that if it's possible to (mostly) neatly map them to multiple returns, that's the most idiomatic Go.
> @evanphx > > > The interface value itself, being the 2 64bit quantities, will store the int itself and the type information. > > I previously (briefly) looked for...
@lann Just not wanting to pick names for things seems like a thin reason to abandon the concept all together. The names, it turns out, rarely matter here because the...
That is a doozy. Well, look at that file it's clear that `tuple` is a bit part of this. For a generic tuple, what we'd probably really like is a...