With HTTP/3 coming, guess we'll finally need a breaking change in the http crate. We made the Version type an opaque struct over an enum to allow adding more versions, but the compiler allows exhaustively matching the opaque struct anyways ;_;
struct Version(Inner); match ver { Version::HTTP_10 | Version::HTTP_11 => (), } (There's a couple more constants, but still, no fallback arm is needed.)
-
-
Is Version::HTTP_10 an associated constant? Ok I see. Yeah it’s weird that the exhaustiveness check can "see through" private fields.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.