On Sunday, 31 January 2016 at 13:59:06 UTC, Robert M. Münch wrote:
I like CTFE and the meta programming idea for languages like D.
However, I'm wondering why most (everyone?) is trying to do
meta-programming using the same language as the one getting
compiled. IMO the use-cases a pretty differ
On Friday, 29 January 2016 at 20:40:18 UTC, Andrei Alexandrescu
wrote:
That'd be interesting if (a) lazy and (b) general a la
https://dlang.org/library/std/range/recurrence.html. -- Andrei
To be clear, by general you mean to allow functions with more
than 2 arguments?
For example if you have
xenon325:
Doesn't http://wiki.dlang.org/DIP25 fix this ?
I think DIP25 is designed to be only a partial solution, it's not
a complete memory safety story.
Bye,
bearophile
Hi all,
I have a non-copyable struct with move semantics. In other words, a
struct with @disable this(this), but with working overloads for the
this(copy) and opAssign.
Now I have an instance of that struct. I would like to be able to
voluntarily give up ownership for the sake of another ins
On 02/02/16 2:21 AM, Shachar Shemesh wrote:
Hi all,
I have a non-copyable struct with move semantics. In other words, a
struct with @disable this(this), but with working overloads for the
this(copy) and opAssign.
Now I have an instance of that struct. I would like to be able to
voluntarily give
On Monday, 1 February 2016 at 13:21:02 UTC, Shachar Shemesh wrote:
Hi all,
I have a non-copyable struct with move semantics. In other
words, a struct with @disable this(this), but with working
overloads for the this(copy) and opAssign.
Now I have an instance of that struct. I would like to b
Am 01.02.2016 um 14:21 schrieb Shachar Shemesh:
Hi all,
I have a non-copyable struct with move semantics. In other words, a
struct with @disable this(this), but with working overloads for the
this(copy) and opAssign.
Now I have an instance of that struct. I would like to be able to
voluntarily
On Monday, 1 February 2016 at 13:21:02 UTC, Shachar Shemesh wrote:
q = std::move(p);
I am unsure what is the correct way to do this under D.
Note that C++ std::move(...) doesn't do anything related to
state, it is only a type cast, so it is zero-overhead.
What I have done to get semantics c
On Monday, 1 February 2016 at 07:13:32 UTC, xenon325 wrote:
On Sunday, 31 January 2016 at 16:18:21 UTC, bearophile wrote:
And currently it's dead-easy to write unsafe code even in
@safe D functions:
int[] foo() pure @safe {
int[2] a = [10, 20];
auto b = a[];
return b;
}
void main()
On Saturday, 30 January 2016 at 17:46:35 UTC, Sean Kelly wrote:
Netty and NIO are an event dispatching mechanism (think
libebevent) backed by a ForkJoinPool. No fibers there. Java
/does/ have fibers in Quasar, though the implementation is a
bit weird because the Java instruction set doesn't sup
http://elm-lang.org/blog/compilers-as-assistants
On Monday, 1 February 2016 at 03:23:18 UTC, Walter Bright wrote:
They have bits and pieces of the info, but nothing about what
is actually generated to, say, catch an exception.
Gotcha, is this something you'd expect to be easily obtainable
(e.g. ask Microsoft Rep saying we want to make it e
I'm not sure what the convention is for resurrecting old threads
but I felt it would be best to start fresh. For reference, the
older thread is here:
http://forum.dlang.org/thread/pyduqwmskkkoicsxi...@forum.dlang.org
tl;dr - I studied a paper with the goal of implementing a stable
3-way parti
On Sunday, 31 January 2016 at 18:52:48 UTC, Steven Schveighoffer
wrote:
2. How does one allocate with an allocator for typed info? In
other words, the GC will call the dtor, but only if it knows
what type you put in there. With std.experimental.allocator,
there isn't a way to do that.
std.all
On Tuesday, 2 February 2016 at 05:04:00 UTC, Jakob Ovrum wrote:
On Sunday, 31 January 2016 at 18:52:48 UTC, Steven
Schveighoffer wrote:
2. How does one allocate with an allocator for typed info? In
other words, the GC will call the dtor, but only if it knows
what type you put in there. With std
15 matches
Mail list logo
