nickajacks1

Thanks for reviewing. Indeed, there's an increased latency on my machine by a few dozen nanoseconds. To put that into perspective, it doesn't register as a blip on my laptop...

> > I'm starting to wonder if there's enough value in this new generics API to warrant implementation and maintenance. For one, it's solving the same problem as v3's Bind,...

I'll try to do a final look over this weekend

Sorry to bring this up again, but I figured I'd try to close the loop on this because the previous discussion kind of fizzled out when the Koa idea was...

Thanks for the feedback. I'll get started. I think that fasthttp gives you enough ways to shoot yourself in the foot that accessing it should be a "use at your...

Since this issue seems to just be caused by the order of route execution, it seems like it can be closed.

One major deviation from Express is the combination of Request and Response into a single Ctx object. It might be worth considering splitting it into a Req and Res object....

I'll play around with my above suggestion in the coming weeks and try to come up with a summary of the impact. I will plan on making a separate issue...

It looks like Ctx.Append has different behavior than res.append in Express. Ctx.Append adds to the existing header field, using comma separators. Example: ``` Vary: Thing1, Thing2 ``` res.append will create...

Agree that if the RFC suggests to use comma separated values for Vary, Fiber should do that. Now that I think about it, I wonder when you'd actually want a...