Louis Pilfold
Louis Pilfold
> It feels like there should be an "escape hatch" (even if you have to write some Erlang) for when you want to receive some non-Gleam messages with potentially any...
It would be a lot more complex, but we could generate an Erlang module at runtime that has a receive function. It would also make creation of a selector a...
We have a special case specifically for process down messages, we could expand it for sockets also. ```erlang {'DOWN', Ref, Kind, Downed, Reason} when is_map_key({Kind, Ref}, Handlers) -> Fn =...
I'd stick with the existing design and have a function for each kind of down message. I don't think there's much in common between ports and processes so we don't...
We'll include a socket module with a definition of a socket type and a monitor function for that. We originally had this for processes and ports, though only the processes...
This library is intended to provide type definitions for all of the core Erlang data types, so it would include sockets. Slightly odd, but that's just the nature of Erlang...
@gleam-lang/emacs-team Any ideas?
Sounds good to me!
You've got the general idea, and that is largely how cowboy websockets work today as I understand. It becomes more complex when you consider the types of messages send to...
Thinking about this more, perhaps it's OK that the typing is not amazing here. If that's a limitation of cowboy it's good motivation to make a Gleam websocket server that...