On Wed, 2016-08-17 at 08:02 +, eugene via Digitalmars-d wrote:
> Hello, everyone,
> will ISO D be in future or not?
I am not sure this would be a good thing. Given the history of Fortran,
C, and C++, avoiding ISO standardization processes would seem to be a
good thing for any other
Is there any way I can log to a terminal or a file from inside an
@nogc function?
Thanks,
Saurabh
On Tuesday, 16 August 2016 at 16:40:30 UTC, Adam D. Ruppe wrote:
On Tuesday, 16 August 2016 at 16:29:18 UTC, Guillaume Piolat
wrote:
Hey, I also stumbled upon this with imageformats decoding PNG.
Image loading makes 10x the garbage it should.
Let's see what this threads unveils...
leet me
On Wednesday, August 17, 2016 09:25:38 eugene via Digitalmars-d wrote:
> is it probably 5 years for ISO D to happen or more?
I don't think that any of us know where D will be in 5 years. Having an ISO
standard at some point is certainly a possibility, but it's not even clear
that it's something
On Wednesday, 17 August 2016 at 03:44:48 UTC, Nick B wrote:
On Monday, 15 August 2016 at 00:42:16 UTC, H. S. Teoh wrote:
On Sun, Aug 14, 2016 at 09:08:31PM +, Nick B via
Digitalmars-d wrote:
While I certainly hope this research would eventually
revolutionize numerical applications, it
On Wednesday, 17 August 2016 at 10:47:35 UTC, qznc wrote:
On Wednesday, 17 August 2016 at 08:02:42 UTC, eugene wrote:
will ISO D be in future or not?
What would be the benefits?
unified language standard?
On Wednesday, 17 August 2016 at 10:47:54 UTC, Guillaume Piolat
wrote:
On Wednesday, 17 August 2016 at 10:45:01 UTC, Saurabh Das wrote:
Is there any way I can log to a terminal or a file from inside
an @nogc function?
Thanks,
Saurabh
import core.stdc.stdio;
printf("am logging C-style\n");
On Wednesday, 17 August 2016 at 11:34:01 UTC, eugene wrote:
On Wednesday, 17 August 2016 at 10:47:35 UTC, qznc wrote:
On Wednesday, 17 August 2016 at 08:02:42 UTC, eugene wrote:
will ISO D be in future or not?
What would be the benefits?
unified language standard?
While the spec might
On Wednesday, 17 August 2016 at 08:02:42 UTC, eugene wrote:
will ISO D be in future or not?
What would be the benefits?
On Wednesday, 17 August 2016 at 10:45:01 UTC, Saurabh Das wrote:
Is there any way I can log to a terminal or a file from inside
an @nogc function?
Thanks,
Saurabh
import core.stdc.stdio;
printf("am logging C-style\n");
On 08/17/2016 04:01 AM, Chris Wright wrote:
> On Tue, 16 Aug 2016 18:55:40 +, Dicebot wrote:
>> You need to add one more level of indirection for things to start going
>> complicated.
>
> Presumably scope is transitive, so things shouldn't get horribly complex.
It is not transitive and it is
On 08/17/2016 10:53 AM, Mike wrote:
> On Wednesday, 17 August 2016 at 07:17:24 UTC, Rory McGuire wrote:
>>
>>> If DIP1000 is implemented, it will change that behavior, so the
>>> allocation will instead be on the GC heap, but the compiler will do some
>>> flow-control analysis to prevent
I have a problem, that .stringof doesn't return what I'm
expecting. Consider the following:
template A(string T)
{
enum A : bool
{
yes = true,
}
}
void main()
{
A!"asdf" a1;
typeof(a1) a2;
mixin(typeof(a1).stringof ~ " a3;");
}
I
On 08/17/2016 02:34 PM, eugene wrote:
> On Wednesday, 17 August 2016 at 10:47:35 UTC, qznc wrote:
>> On Wednesday, 17 August 2016 at 08:02:42 UTC, eugene wrote:
>>> will ISO D be in future or not?
>>
>> What would be the benefits?
>
> unified language standard?
Unified among whom? There is only
Jacob Carlborg put together a guest post describing the history
and implementation of D Version manager. If you've never heard of
it, take a look. It's a useful utility to have installed.
Blog:
https://dlang.org/blog/2016/08/17/inside-d-version-manager/
Reddit:
On Tuesday, 16 August 2016 at 20:19:32 UTC, ketmar wrote:
On Tuesday, 16 August 2016 at 20:11:12 UTC, Yuxuan Shui wrote:
Wait, doesn't D have strict aliasing rules?
luckily, no. at least this is not enforced by dmd. and it is
great.
Controlling aliasing is really the #1 optimization
On Wednesday, 17 August 2016 at 07:48:02 UTC, kookman wrote:
I was interested low(er) cost logging and stumbled across a
proposal by Max Klimov from about 16 months ago to add an
AsyncLogger to std.experimental.logger (ref
http://forum.dlang.org/thread/lcsjtxorbbagmbvbl...@forum.dlang.org).
On Wednesday, 17 August 2016 at 06:51:51 UTC, Ethan Watson wrote:
On Tuesday, 16 August 2016 at 17:53:20 UTC, Meta wrote:
On Tuesday, 16 August 2016 at 12:30:14 UTC, Ethan Watson wrote:
Looking through your slides, I noticed that there's no need to
pass `typeof(this)` to GenerateStubsFor.
On Wednesday, 17 August 2016 at 12:20:28 UTC, deadalnix wrote:
On Tuesday, 16 August 2016 at 20:19:32 UTC, ketmar wrote:
On Tuesday, 16 August 2016 at 20:11:12 UTC, Yuxuan Shui wrote:
Wait, doesn't D have strict aliasing rules?
luckily, no. at least this is not enforced by dmd. and it is
On Wednesday, 17 August 2016 at 10:43:01 UTC, Russel Winder wrote:
On Wed, 2016-08-17 at 08:02 +, eugene via Digitalmars-d
wrote:
Hello, everyone,
will ISO D be in future or not?
I am not sure this would be a good thing. Given the history of
Fortran, C, and C++, avoiding ISO
On Wednesday, 17 August 2016 at 12:32:20 UTC, ketmar wrote:
from my PoV, this kind of "optimizing" is overrated. i'm
absolutely unable to understand why should i obey orders from
machine instead of machine obeys my orders. if i want to go
wild with pointers, don't tell me that i can't, just
On 2016-08-16 17:08, ZombineDev wrote:
Swift developers, on the other hand, explicitly state that they don't
want to support any form compile-time metaprogramming: [5]. Ironically
they make heavy use of it in their standard-library. However instead of
writing the meta code in Swift, they use
On Wednesday, 17 August 2016 at 07:17:24 UTC, Rory McGuire wrote:
If DIP1000 is implemented, it will change that behavior, so
the
allocation will instead be on the GC heap, but the compiler
will do some
flow-control analysis to prevent escaping references. Is that
right?
Mike
Not
On 08/17/2016 02:08 PM, Eugene Wissner wrote:
I have a problem, that .stringof doesn't return what I'm expecting.
Consider the following:
template A(string T)
{
enum A : bool
{
yes = true,
}
}
void main()
{
A!"asdf" a1;
typeof(a1) a2;
mixin(typeof(a1).stringof ~
https://issues.dlang.org/show_bug.cgi?id=16398
Issue ID: 16398
Summary: aligned allocator: aligned reallocation is not defined
Product: D
Version: D2
Hardware: All
OS: All
Status: NEW
Severity: enhancement
// -- Example: --
template A(alias Arg) {
enum A = Arg;
enum Unrelated = ({return 0;})(); // this line prevent
compilation
};
void main() {
enum FnPtr =
enum _ = A!FnPtr;
};
void asdf() {};
// ( https://dpaste.dzfl.pl/79301f12e5fc )
Just by having a
On Wednesday, 17 August 2016 at 13:09:40 UTC, Cauterite wrote:
Just by having a random `({return 0;})()` in the template body,
suddenly the template rejects its arguments. I'm so confused,
is this a bug? Or am I missing something?
Function pointers and delegates are not valid compile time
On Wed, 17 Aug 2016 13:53:37 +0300, Dicebot wrote:
> On 08/17/2016 04:01 AM, Chris Wright wrote:
>> On Tue, 16 Aug 2016 18:55:40 +, Dicebot wrote:
>>> You need to add one more level of indirection for things to start
>>> going complicated.
>>
>> Presumably scope is transitive, so things
On Wednesday, 17 August 2016 at 13:18:06 UTC, Adam D. Ruppe wrote:
Best you can do is use them in an alias argument directly, but
you cannot use them in an enum argument.
I think you missed the point; it works perfectly fine without
having this `({return 0;})()` in the template body (which,
On Wednesday, 17 August 2016 at 12:20:28 UTC, deadalnix wrote:
Controlling aliasing is really the #1 optimization barrier
these days, so I don't think it's that good of a thing.
Almost every single one case where Rust end up being faster
than C++ is because their type system allow for more
On 17.08.2016 15:41, jmh530 wrote:
On Wednesday, 17 August 2016 at 12:20:28 UTC, deadalnix wrote:
Controlling aliasing is really the #1 optimization barrier these days,
so I don't think it's that good of a thing.
Almost every single one case where Rust end up being faster than C++
is because
On Wednesday, 17 August 2016 at 14:19:08 UTC, Dejan Lekic wrote:
On Wednesday, 17 August 2016 at 12:57:59 UTC, TencoDK wrote:
I dropped D once about a year ago because the new DMD version
has broken backward compatibility. Some libraries have stopped
You could have used STABLE DMD (v1),
On Wednesday, 17 August 2016 at 13:41:09 UTC, jmh530 wrote:
On Wednesday, 17 August 2016 at 12:20:28 UTC, deadalnix wrote:
Controlling aliasing is really the #1 optimization barrier
these days, so I don't think it's that good of a thing.
Almost every single one case where Rust end up being
https://issues.dlang.org/show_bug.cgi?id=16390
Cauterite changed:
What|Removed |Added
CC||cauter...@gmail.com
---
On Wednesday, 17 August 2016 at 13:33:26 UTC, Steven
Schveighoffer wrote:
I think the OP's case is a bug. Please file.
Thanks, I've filed it. Just wanted to get a second opinion before
concluding that it's a bug.
On 8/17/16 10:38 AM, deadalnix wrote:
On Wednesday, 17 August 2016 at 14:21:32 UTC, Steven Schveighoffer wrote:
void * is almost useless. In D you can assign a void[] from another
void[], but other than that, there's no way to write the memory or
read it.
In C, void * is also allowed to alias
On Tue, 16 Aug 2016 19:59:16 +, Karabuta wrote:
> Looking through documentations for the various packages available in the
> dub registry, I noticed that some packages have very good documentation
> whilst others are quite not there yet. ...
>
> Therefore I suggest the community put-up some
https://issues.dlang.org/show_bug.cgi?id=16399
Issue ID: 16399
Summary: template with func. ptr. argument and anon. func. in
the template body, rejects its argument
Product: D
Version: D2
Hardware: All
OS:
On 8/16/16 7:23 PM, Charles Hixson via Digitalmars-d wrote:
On 08/16/2016 01:49 PM, Steven Schveighoffer via Digitalmars-d wrote:
On 8/16/16 4:11 PM, Yuxuan Shui wrote:
Wait, doesn't D have strict aliasing rules? ubyte* () should not be
allowed to alias with ubyte** ().
Even if it did, I
On Wednesday, 17 August 2016 at 14:21:32 UTC, Steven
Schveighoffer wrote:
void * is almost useless. In D you can assign a void[] from
another void[], but other than that, there's no way to write
the memory or read it.
In C, void * is also allowed to alias any other pointer. But
char * is
https://issues.dlang.org/show_bug.cgi?id=16400
Cauterite changed:
What|Removed |Added
Keywords||iasm, wrong-code
--
https://issues.dlang.org/show_bug.cgi?id=16400
Issue ID: 16400
Summary: naked variadic C function emits broken prologue
Product: D
Version: D2
Hardware: x86
OS: Windows
Status: NEW
Severity: normal
On Wed, 17 Aug 2016 14:28:24 +, TencoDK wrote:
> On Wednesday, 17 August 2016 at 14:19:08 UTC, Dejan Lekic wrote:
>> On Wednesday, 17 August 2016 at 12:57:59 UTC, TencoDK wrote:
>>>
>>> I dropped D once about a year ago because the new DMD version has
>>> broken backward compatibility. Some
How about the specific case of array indexing?
Is it UB to have `arr[i]` ever point into `arr` itself, or can we
make it UB?
-Johan
On Wednesday, 17 August 2016 at 12:39:18 UTC, ag0aep6g wrote:
On 08/17/2016 02:08 PM, Eugene Wissner wrote:
I have a problem, that .stringof doesn't return what I'm
expecting.
Consider the following:
template A(string T)
{
enum A : bool
{
yes = true,
}
}
void main()
{
On Tuesday, 16 August 2016 at 21:05:29 UTC, jmh530 wrote:
On Tuesday, 16 August 2016 at 19:59:16 UTC, Karabuta wrote:
Looking through documentations for the various packages
available in the dub registry, I noticed that some packages
have very good documentation whilst others are quite not
On Wednesday, 17 August 2016 at 13:21:16 UTC, Cauterite wrote:
On Wednesday, 17 August 2016 at 13:18:06 UTC, Adam D. Ruppe
wrote:
Best you can do is use them in an alias argument directly, but
you cannot use them in an enum argument.
I think you missed the point; it works perfectly fine
On 8/17/16 9:23 AM, Lodovico Giaretta wrote:
On Wednesday, 17 August 2016 at 13:21:16 UTC, Cauterite wrote:
On Wednesday, 17 August 2016 at 13:18:06 UTC, Adam D. Ruppe wrote:
Best you can do is use them in an alias argument directly, but you
cannot use them in an enum argument.
I think you
On Wednesday, 17 August 2016 at 12:57:59 UTC, TencoDK wrote:
I dropped D once about a year ago because the new DMD version
has broken backward compatibility. Some libraries have stopped
You could have used STABLE DMD (v1), right? Assuming that you
*intentionally* used the unstable (v2) DMD,
On Wed, Aug 17, 2016 at 03:44:48AM +, Nick B via Digitalmars-d wrote:
> On Monday, 15 August 2016 at 00:42:16 UTC, H. S. Teoh wrote:
[...]
> > Thanks to operator overloading and alias this, we can probably do a
> > pretty good job implementing unums as a library so that people can
> > try it
Just a small update today.
if(__ctfe) and if(!__ctfe)
now get special treatment.
Also working on getting compiletime-parsers to run.
On Wednesday, 17 August 2016 at 08:37:32 UTC, Lodovico Giaretta
wrote:
On Tuesday, 16 August 2016 at 23:18:28 UTC, Adam D. Ruppe wrote:
On Tuesday, 16 August 2016 at 19:17:27 UTC, Engine Machine
wrote:
alias x = AliasSeq!(a, b, AliasSeq!(c, d));
results in a flat sequence. I would like to be
On 17 Aug 2016 18:50, "Stefan Koch via Digitalmars-d-announce" <
digitalmars-d-announce@puremagic.com> wrote:
>
> Just a small update today.
> if(__ctfe) and if(!__ctfe)
> now get special treatment.
> Also working on getting compiletime-parsers to run.
>
Nice tease with the "compile time parsers
https://issues.dlang.org/show_bug.cgi?id=16390
b2.t...@gmx.com changed:
What|Removed |Added
CC|b2.t...@gmx.com |
--
I'm wondering whether there is such a thing as single-use of a type in
compiler technology. I think if the compiler could determine that a type
is used only once, it could apply optimizations.
A colleague of mine raised the issue of D's use of the GC even for
seemingly local delegates. For
On Wed, 17 Aug 2016 22:12:25 +, Yuxuan Shui wrote:
> But doing so would be incorrect if D doesn't provide strong aliasing
> guarantees. And if D does provide these guarantees, we won't need to do
> this manually.
The language can analyze all code that affects a local variable in many
cases.
On Thursday, 18 August 2016 at 03:54:24 UTC, WhatMeWorry wrote:
When I saw the .dll in OpenGL.dll, I immediately thought: just
Windows. But does this hold true for the linux shared opengl
libraries as well? Is this why DerelictGL3.reload() does not
take a path argument. But then why
On Wednesday, 17 August 2016 at 13:27:14 UTC, deadalnix wrote:
Especially since there are already ways to do this is a way
that makes the AA happy
exactly the thing i was writing about. "hey, you, meatbag! i, Teh
Great Machine, said that you have to use unions, not pointers!
what? making a
On Wednesday, 17 August 2016 at 19:36:17 UTC, Walter Bright wrote:
On 8/17/2016 5:20 AM, deadalnix wrote:
Controlling aliasing is really the #1 optimization barrier
these days, so I
don't think it's that good of a thing.
Almost every single one case where Rust end up being faster
than C++ is
On Wednesday, 17 August 2016 at 18:24:37 UTC, Rory McGuire wrote:
On 17 Aug 2016 18:50, "Stefan Koch via Digitalmars-d-announce"
< digitalmars-d-announce@puremagic.com> wrote:
Just a small update today.
if(__ctfe) and if(!__ctfe)
now get special treatment.
Also working on getting
On Wednesday, 17 August 2016 at 19:15:48 UTC, ag0aep6g wrote:
On 08/17/2016 08:38 PM, Engine Machine wrote:
On Wednesday, 17 August 2016 at 08:37:32 UTC, Lodovico
Giaretta wrote:
[...]
You mean something like:
struct MySequence(Args...)
{
enum length = Args.length;
alias args = Args;
On Wednesday, 17 August 2016 at 18:38:48 UTC, Engine Machine
wrote:
On Wednesday, 17 August 2016 at 08:37:32 UTC, Lodovico Giaretta
wrote:
On Tuesday, 16 August 2016 at 23:18:28 UTC, Adam D. Ruppe
wrote:
[...]
You mean something like:
struct MySequence(Args...)
{
enum length =
On Wednesday, 17 August 2016 at 19:15:48 UTC, ag0aep6g wrote:
On 08/17/2016 08:38 PM, Engine Machine wrote:
[...]
[...]
[...]
With MySequence being a type, you can do this:
static if (is(x.args[2] == MySequence!Args, Args ...))
{
...
}
It works! Nifty that you can do that
On 8/17/2016 5:20 AM, deadalnix wrote:
Controlling aliasing is really the #1 optimization barrier these days, so I
don't think it's that good of a thing.
Almost every single one case where Rust end up being faster than C++ is because
their type system allow for more AA information available for
On 08/17/2016 08:38 PM, Engine Machine wrote:
On Wednesday, 17 August 2016 at 08:37:32 UTC, Lodovico Giaretta wrote:
[...]
You mean something like:
struct MySequence(Args...)
{
enum length = Args.length;
alias args = Args;
}
alias x = MySequence!(a, b, MySequence!(c, d));
static
On Wednesday, 17 August 2016 at 11:34:01 UTC, eugene wrote:
On Wednesday, 17 August 2016 at 10:47:35 UTC, qznc wrote:
On Wednesday, 17 August 2016 at 08:02:42 UTC, eugene wrote:
will ISO D be in future or not?
What would be the benefits?
unified language standard?
As a former Common Lisp
https://rogeralsing.com/2016/08/16/wire-writing-one-of-the-fastest-net-serializers/
It's interesting to compare what C# does and what people do in C#
to promote speed over obviousness of implementation, with what D
does by default and what's natural to do in D.
A direct comparison isn't
On Wednesday, 17 August 2016 at 19:21:57 UTC, Lodovico Giaretta
wrote:
On Wednesday, 17 August 2016 at 19:15:48 UTC, ag0aep6g wrote:
[...]
import std.traits: TemplateOf;
static if (__traits(isSame, TemplateOf!(x.args[2]), MySequence))
{
...
}
std.traits.TemplateOf extracts the symbol
On 08/17/2016 09:21 PM, Lodovico Giaretta wrote:
import std.traits: TemplateOf;
static if (__traits(isSame, TemplateOf!(x.args[2]), MySequence))
{
...
}
std.traits.TemplateOf extracts the symbol representing the
uninstantiated template.
__traits(isSame, symbol1, symbol2) evaluates at
On Monday, 15 August 2016 at 22:33:26 UTC, Brad Roberts wrote:
Network connectivity issues. That set of machines runs out of
my house and the comcast connection isn't happy, apparently.
On 8/15/16 12:55 PM, Lodovico Giaretta via Digitalmars-d wrote:
I don't know much about PRs and the
On 2016-08-15 22:28, NX wrote:
https://issues.dlang.org/show_bug.cgi?id=14859
This limitation is put there because of optlink (which fails to link
when you have enough static data), and is actually entirely meaningless
when combined with -m32mscoff & -m64 switches (since other linkers
handle
On Wednesday, 17 August 2016 at 06:44:41 UTC, Mike wrote:
On Wednesday, 17 August 2016 at 04:28:33 UTC, Rory McGuire
wrote:
Basically DIP1000 makes it so that:
void main()
{
A obj;
{
scope A a = new A(1);
obj = a;
}
assert(obj.x == 1); // fails, 'a' has been
On Wednesday, 17 August 2016 at 08:48:12 UTC, Jonathan M Davis
wrote:
On Wednesday, August 17, 2016 08:02:42 eugene via Digitalmars-d
wrote:
Hello, everyone,
will ISO D be in future or not?
The future? Maybe. But it's unlikely to happen soon. As a
whole, the language is pretty solid, but
On Wednesday, 17 August 2016 at 06:27:39 UTC, Jacob Carlborg
wrote:
Windows only or cross-platform?
It will be cross platform, but right now I've only developed on
Windows. Linux will be next, I have Mint setup at home. I'll
likely need an external contributor for PS4, but that could very
I was interested low(er) cost logging and stumbled across a
proposal by Max Klimov from about 16 months ago to add an
AsyncLogger to std.experimental.logger (ref
http://forum.dlang.org/thread/lcsjtxorbbagmbvbl...@forum.dlang.org). The resulting PR 3194 has been dormant for some time. I was
On Tuesday, 16 August 2016 at 23:18:28 UTC, Adam D. Ruppe wrote:
On Tuesday, 16 August 2016 at 19:17:27 UTC, Engine Machine
wrote:
alias x = AliasSeq!(a, b, AliasSeq!(c, d));
results in a flat sequence. I would like to be able to keep
them separate so I can have sub sequences.
wrap them in
On Wednesday, 17 August 2016 at 07:53:49 UTC, Mike wrote:
Got it! Thank you! But it still appears that what's
illustrated on the deprecations page is not being deprecated.
Mike
I imagine that will change if/when DIP1000 is accepted.
On 2016-08-16 14:30, Ethan Watson wrote:
https://github.com/Remedy-Entertainment/binderoo
So I just announced at GDC Europe in my talk. We're open sourcing our
binding system.
It's currently a complete reengingeering of the system, and it's
incomplete at the moment. It will be documented as
On Wednesday, 17 August 2016 at 07:04:26 UTC, Mike wrote:
Or perhaps DIP1000 changes the current behavior of the `scope`
storage class.
My understanding is that the `scope` storage class currently
allocates a class on the stack (though its usage for this
purpose is deprecated in favor of
On Tuesday, 16 August 2016 at 15:31:20 UTC, Meta wrote:
Did you get a decent crowd despite giving your talk at the same
time as John Romero?
Estimate of about 80-100 people.
Romero is a nice guy though. http://i.imgur.com/kTrfAZqh.jpg
On Wednesday, 17 August 2016 at 04:28:33 UTC, Rory McGuire wrote:
Basically DIP1000 makes it so that:
void main()
{
A obj;
{
scope A a = new A(1);
obj = a;
}
assert(obj.x == 1); // fails, 'a' has been destroyed
}
Will not compile.
Ok, that makes sense. But
Hello, everyone,
will ISO D be in future or not?
No, same here, but one day ago it worked ok for me.
Dne 17.8.2016 v 11:32 Arjan via Digitalmars-d napsal(a):
On Tuesday, 16 August 2016 at 14:31:54 UTC, Ethan Watson wrote:
Slides are up at
http://www.slideshare.net/EthanWatson5/d-using-an-emerging-language-in-quantum-break
I'm getting an
On Wednesday, 17 August 2016 at 09:25:38 UTC, eugene wrote:
is it probably 5 years for ISO D to happen or more?
On the topic:
https://forum.dlang.org/thread/wzifwqtytvkqmecbf...@forum.dlang.org
On Tuesday, 16 August 2016 at 17:53:20 UTC, Meta wrote:
On Tuesday, 16 August 2016 at 12:30:14 UTC, Ethan Watson wrote:
Looking through your slides, I noticed that there's no need to
pass `typeof(this)` to GenerateStubsFor.
Correct. Notice a few slides after that with the BindAllImports
On Tuesday, 16 August 2016 at 14:31:54 UTC, Ethan Watson wrote:
Slides are up at
http://www.slideshare.net/EthanWatson5/d-using-an-emerging-language-in-quantum-break
I'm getting an error and can't see the slide content. Is it just
me?
On Tuesday, 16 August 2016 at 07:19:18 UTC, Edwin van Leeuwen
wrote:
I am using:
http://code.dlang.org/packages/docopt
It's not really json configurable, but that shouldn't be to
complex to implement yourself.
That's also very nice. I hadn't thought of writing the help text
first and then
On Wed, Aug 17, 2016 at 9:04 AM, Mike via Digitalmars-d-announce <
digitalmars-d-announce@puremagic.com> wrote:
>
>
> Or perhaps DIP1000 changes the current behavior of the `scope` storage
> class.
>
> My understanding is that the `scope` storage class currently allocates a
> class on the stack
On Wednesday, August 17, 2016 08:02:42 eugene via Digitalmars-d wrote:
> Hello, everyone,
> will ISO D be in future or not?
The future? Maybe. But it's unlikely to happen soon. As a whole, the
language is pretty solid, but there are details that still need to be ironed
out spec-wise, there are a
But this works:
http://www.slideshare.net/EthanWatson5/
Dne 17.8.2016 v 11:32 Arjan via Digitalmars-d napsal(a):
On Tuesday, 16 August 2016 at 14:31:54 UTC, Ethan Watson wrote:
Slides are up at
http://www.slideshare.net/EthanWatson5/d-using-an-emerging-language-in-quantum-break
I'm getting
On Wednesday, 17 August 2016 at 22:59:31 UTC, WhatMeWorry wrote:
I want to store all my shared/dynamic libraries within a
special directory relative to where the application directory
is. All of the derelictXX.loads(path) compiles except
DerelictGL3.reload(lib); which doesn't seem to be
On 08/18/2016 12:25 AM, Ali Çehreli wrote:
> I'm wondering whether there is such a thing as single-use of a type in
> compiler technology. I think if the compiler could determine that a type
> is used only once, it could apply optimizations.
>
> A colleague of mine raised the issue of D's use of
On 8/17/2016 4:13 PM, Brad Roberts via Digitalmars-d wrote:
Several of the machines are run out of aws. The cost of running a windows
instance inside aws is pretty awful. Shrug.. it's a wash, for the most part.
For the ones in house, I wonder if it would be cost effective to replace them
On 8/17/16 3:27 PM, wobbles via Digitalmars-d wrote:
On Monday, 15 August 2016 at 22:33:26 UTC, Brad Roberts wrote:
Network connectivity issues. That set of machines runs out of my house and the
comcast connection
isn't happy, apparently.
On 8/15/16 12:55 PM, Lodovico Giaretta via
https://en.wikipedia.org/wiki/Virtual_class
Can D do stuff like this naturally?
On Thursday, 18 August 2016 at 00:20:32 UTC, Chris Wright wrote:
On Wed, 17 Aug 2016 22:12:25 +, Yuxuan Shui wrote:
But doing so would be incorrect if D doesn't provide strong
aliasing guarantees. And if D does provide these guarantees,
we won't need to do this manually.
The language can
On 8/17/16 4:47 PM, Walter Bright via Digitalmars-d wrote:
On 8/17/2016 4:13 PM, Brad Roberts via Digitalmars-d wrote:
Several of the machines are run out of aws. The cost of running a windows
instance inside aws is pretty awful. Shrug.. it's a wash, for the most part.
For the ones in
On Thursday, 18 August 2016 at 00:59:43 UTC, Dicebot wrote:
On 08/18/2016 12:25 AM, Ali Çehreli wrote:
[...]
I believe actual reason is that aliased lambda has to allocate
a closure because it refers to stack local variable (limit).
This compiles just fine:
auto countAbove(int[] a, int
On Thursday, 18 August 2016 at 02:51:48 UTC, Meta wrote:
On Thursday, 18 August 2016 at 00:49:49 UTC, Engine Machine
wrote:
https://en.wikipedia.org/wiki/Virtual_class
Can D do stuff like this naturally?
Yes, D's `alias this` feature supports this.
On Thursday, 18 August 2016 at 03:11:17 UTC, WhatMeWorry wrote:
On Wednesday, 17 August 2016 at 23:21:59 UTC, Rene Zwanenburg
wrote:
On Wednesday, 17 August 2016 at 22:59:31 UTC, WhatMeWorry
wrote:
I want to store all my shared/dynamic libraries within a
special directory relative to where the
1 - 100 of 111 matches
Mail list logo