Is this planned at all? And if I was interested in implementing it myself, where would I start?
贡献者指南
技术栈
go
领域
backendperformance
议题类型
feature
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
5
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
over 1 week
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
needs maintainer response
清晰度议题是否清楚说明期望改动、验收标准和下一步。
mostly clear
前置要求
Go programmingHTTP/2 protocol knowledgefasthttp API understanding
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
15
研究方向
Review the 67 comments on this issue for prior discussion and potential implementation approaches. Examine the fasthttp codebase, focusing on the existing HTTP/1.x handling in files like server.go and client.go. Investigate how other Go HTTP libraries (e.g., net/http) implement HTTP/2 support, particularly the use of golang.org/x/net/http2. Propose a design that integrates HTTP/2 without compromising fasthttp's zero alloc high performance model. Since the issue is open and the maintainer has not committed to the feature, first clarify whether the maintainer would accept a PR and what design constraints exist.
