On Sunday, 29 November 2015 at 09:12:14 UTC, tired_eyes wrote:
On Sunday, 29 November 2015 at 09:05:37 UTC, tcak wrote:
On Sunday, 29 November 2015 at 08:56:30 UTC, tired_eyes wrote:
I was a bit surprised to see that std.socket is deprecated as
of 2.069. Just curious, what's wrong with it? And what should
I use as a replacement? I know there is vibe.socket, but I
don't want to include fullstack web framework as a dependency
just to make some HTTP reqests.
I also don't see any proposed replacements in a review queue.
Will std.socket and std.socketstream be just thrown away?
I would say "WTF" at first, then checked the documentation,
but don't see anything
about deprecation. My current whole business relies on that.
Wow, sorry, I meant std.stream and std.socketstream, not
std.socket and std.socketstream
std.stream, and the stream interface in general, is deprecated in
favor of ranges, which are more generic and flexible.
