I have been reading the D forums for a while and following on its
amazing progress for a long time. Over time I have even written
some basic D programs for myself, nothing major or earth
shuttering. I have downloaded and read Ali's excellent book.
I would like to dive deeper into D, however s
Hello. I run program through std.process.pipeShell and want to
read from it stdout in loop. How do this non-blocking?
I try
int fd = p.stdout.fileno;
int flags = fcntl(fd, F_GETFL, 0);
flags |= O_NONBLOCK;
fcntl(fd, F_SETFL, flags);
but get error "Resource tempo
Does anyone have any good reads on the subject of statically
choosing suitable hash-functions depending on the type (and in
turn size) of the key?
I wonder because I'm currently experimenting with a hash set
implementation at
https://github.com/nordlow/phobos-next/blob/40e2973b74d58470a13a5a
On 10/2/17 2:31 PM, Per Nordlöw wrote:
On Monday, 2 October 2017 at 18:14:24 UTC, Jacob Carlborg wrote:
On 2017-10-02 17:57, Nordlöw wrote:
Is implementing opCall(size_t) for structures such as array
containers that already define opIndex and opSlice deprecated?
I can't find any documentation
On Monday, October 02, 2017 18:31:23 Per Nordlöw via Digitalmars-d-learn
wrote:
> On Monday, 2 October 2017 at 18:14:24 UTC, Jacob Carlborg wrote:
> > On 2017-10-02 17:57, Nordlöw wrote:
> >> Is implementing opCall(size_t) for structures such as array
> >> containers that already define opIndex an
On Monday, 2 October 2017 at 18:14:24 UTC, Jacob Carlborg wrote:
On 2017-10-02 17:57, Nordlöw wrote:
Is implementing opCall(size_t) for structures such as array
containers that already define opIndex and opSlice deprecated?
I can't find any documentation on the subject on when opCall
should b
On 2017-10-02 17:57, Nordlöw wrote:
Is implementing opCall(size_t) for structures such as array containers
that already define opIndex and opSlice deprecated?
I can't find any documentation on the subject on when opCall should be
defined to enable foreach (isIterable).
opCall is not related
Is implementing opCall(size_t) for structures such as array
containers that already define opIndex and opSlice deprecated?
I can't find any documentation on the subject on when opCall
should be defined to enable foreach (isIterable).
On Monday, 2 October 2017 at 09:34:29 UTC, Andrea Fontana wrote:
Anyway: you cant put a default destructor on struct
True. In which case you should either @disable this() (which
presents its own set of issues) or hide b behind a @property
function, something like:
struct S {
B _b;
On Monday, 2 October 2017 at 09:08:59 UTC, Biotronic wrote:
Not knowing what you're attempting to do, I'm not sure how to
fix your problem. But if what I've described above does indeed
cover it, initializing b in the constructor is the way to get
it to work.
--
Biotronic
Obviusly real exa
On Monday, 2 October 2017 at 08:47:47 UTC, Andrea Fontana wrote:
Why this code doesn't write two identical lines?
https://dpaste.dzfl.pl/e99aad315a2a
Andrea
A reduced example of where it goes wrong:
class B {}
struct A {
B b = new B;
}
unittest {
A a1, a2;
assert(a1 == a2);
}
Why this code doesn't write two identical lines?
https://dpaste.dzfl.pl/e99aad315a2a
Andrea
12 matches
Mail list logo