-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Any way to build with gotip
?
#3757
Comments
I hear you. qlts is a pain. More context: #2727 But I have good news for you. If everything goes according to plan, we won’t need it any more for Go 1.21! crypto/tls is gaining a QUIC API (golang/go#44886), and with a little bit of luck, we’ll even get this extended to support 0-RTT (which would be a requirement for quic-go). |
Oooh, nice. Just read through that issue, very fascinating API discussion. So in theory, from my reading, when the |
Almost:
|
Because of
qtls
, I'm not able to build Caddy withgotip
to test some upcoming functionality in Go.Is there any possible workaround to make builds work? Is my only option to fork
qtls
to hack in a fix to make the Go 1.20 qtls apply to Go 1.21 as well?Semi-relatedly, this has been a point of friction with Caddy releases, users tend to want to try to build Caddy with the latest version of Go right away, but usually we need to update our
quic-go
dependency before they're able to do so, and sometimes (understandably) that isn't ready right away when Go releases.Is there any reason that
qtls
can't be prepared well ahead of time to support the next Go version, possibly with a warning in place instead of an error, saying that the APIs are possibly subject to change?The text was updated successfully, but these errors were encountered: