On Sunday, 29 November 2015 at 18:00:34 UTC, tired_eyes wrote:
On Sunday, 29 November 2015 at 16:10:22 UTC, Alex Parrill wrote:
std.stream, and the stream interface in general, is deprecated
in favor of ranges, which are more generic and flexible.
Could you please give a small example?
Conside
On Sunday, 29 November 2015 at 16:10:22 UTC, Alex Parrill wrote:
std.stream, and the stream interface in general, is deprecated
in favor of ranges, which are more generic and flexible.
Could you please give a small example?
Consider this minimal app:
import std.stdio;
import std.socket;
impor
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
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
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
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
