Scope of this library, stdlib integration about http HOT 4 CLOSED

The problem with reimplementing it is that you would not be compatible with other HTTP using libraries as types in Gleam are nominal rather than structural. There would be a lot of added boilerplate.

I'm not yet sure if this library should be merged into the stdlib, more thought is needed.

RE Request and Response: we could implement these two types in many different ways so I'm not sure these are as suitable for being shared. If we do come up with an overarching abstraction I would like to consider how it works for HTTP 1, 2, and 3, how SSE works, and how middleware + error handling works. Without answers for so these I don't think we have an abstraction to share yet

from http.

I like where this has gone, is there anything I can help with for a new hex release. Midas is currently on my old shared message type, but I can't use this in a package I publish to hex yet.

from http.

Let's cut a release and see how it goes. Thanks for the nudge!

from http.

https://hex.pm/packages/gleam_http/1.1.0

from http.