Re: `this` and nested structs

On Thursday, 10 May 2018 at 03:23:50 UTC, Mike Franklin wrote: Consider the following code: --- struct S { // intentionally not `static` struct SS { int y() { return x; } // Error: need `this` for `x` of type `int` } int x; SS ss; } void main() { S s;

`this` and nested structs

Consider the following code: --- struct S { // intentionally not `static` struct SS { int y() { return x; } // Error: need `this` for `x` of type `int` } int x; SS ss; } void main() { S s; s.ss.y(); } --- If I change `return x;` to `return this.x;`

Re: Binderoo additional language support?

On 05/09/2018 03:50 PM, Ethan wrote: On Tuesday, 8 May 2018 at 14:28:53 UTC, jmh530 wrote: I don't really understand what to use binderoo for. So rather than fill out the questionnaire, maybe I would just recommend you do some work on wiki, blog post, or simple examples. Been putting that

Re: D GPU execution module: A survey of requirements.

On Thursday, 10 May 2018 at 00:10:07 UTC, H Paterson wrote: Welp... It's not quite what I would have envisioned, but seems to fill the role. Thanks for pointing Dcompute out to me - I only found it mentioned in a dead link on the D wiki. Time to find a new project... I'm sure the people

Re: Binderoo additional language support?

On Wednesday, 9 May 2018 at 19:50:41 UTC, Ethan wrote: Been putting that off until the initial proper stable release, it's still in a pre-release phase. But tl;dr - It acts as an intermediary layer between a host application written in C++/.NET and libraries written in D. And as it's

Re: D GPU execution module: A survey of requirements.

On Wednesday, 9 May 2018 at 23:37:14 UTC, Henry Gouk wrote: On Wednesday, 9 May 2018 at 23:26:19 UTC, H Paterson wrote: Hello, I'm interested in writing a module for executing D code on GPUs. I'd like to bounce some ideas off D community members to see what this module needs do. [...]

[Issue 15609] Populate vtable in debuginfo

https://issues.dlang.org/show_bug.cgi?id=15609 --- Comment #1 from Manu --- MSVC emits the vptr as "__vfptr", which is a pointer to an array of void* Please have DMD match this array of void* convention, so we can inspect the state of the vtable in D just the same as in

Re: D GPU execution module: A survey of requirements.

On Wednesday, 9 May 2018 at 23:26:19 UTC, H Paterson wrote: Hello, I'm interested in writing a module for executing D code on GPUs. I'd like to bounce some ideas off D community members to see what this module needs do. What about DCompute project? [...]

Re: D GPU execution module: A survey of requirements.

On Wednesday, 9 May 2018 at 23:26:19 UTC, H Paterson wrote: Hello, I'm interested in writing a module for executing D code on GPUs. I'd like to bounce some ideas off D community members to see what this module needs do. [...] Check out https://github.com/libmir/dcompute

D GPU execution module: A survey of requirements.

Hello, I'm interested in writing a module for executing D code on GPUs. I'd like to bounce some ideas off D community members to see what this module needs do. I'm conducting this survey in case my project becomes sufficiently developed to be contributed to the D standard library. I'd

Re: Simple web server benchmark - vibe.d is slower than node.js and Go?

On Wednesday, 9 May 2018 at 21:55:15 UTC, Daniel Kozak wrote: On which system? AFAIK HTTPServerOption.reusePort works on Linux but maybe not on others OSes. Other question is what events driver is use (libasync, libevent, vibe-core) On Wed, May 9, 2018 at 9:12 PM, Arun Chandrasekaran via

Re: is the ubuntu sourceforge repository safe?

On Tuesday, 1 August 2017 at 10:01:17 UTC, Michael wrote: On Monday, 24 July 2017 at 11:02:55 UTC, Russel Winder wrote: On Sun, 2017-07-23 at 18:23 +, Michael via Digitalmars-d wrote: I stopped using it. It kept causing error messages in my package manager and I couldn't update it

Re: Simple web server benchmark - vibe.d is slower than node.js and Go?

On which system? AFAIK HTTPServerOption.reusePort works on Linux but maybe not on others OSes. Other question is what events driver is use (libasync, libevent, vibe-core) On Wed, May 9, 2018 at 9:12 PM, Arun Chandrasekaran via Digitalmars-d < digitalmars-d@puremagic.com> wrote: > On Monday, 30

[Issue 18845] Extern(C++) class with no virtual functions

https://issues.dlang.org/show_bug.cgi?id=18845 --- Comment #2 from Manu --- What does "safe casting" mean? You mean that it might require pointer adjustment? I mean, it's absolutely necessary that when casting extern(C++) classes, that some special logic is applied which

[Issue 18846] New: VisualD - show vtable in debugger

https://issues.dlang.org/show_bug.cgi?id=18846 Issue ID: 18846 Summary: VisualD - show vtable in debugger Product: D Version: D2 Hardware: All OS: All Status: NEW Severity: enhancement Priority:

[Issue 18845] Extern(C++) class with no virtual functions

https://issues.dlang.org/show_bug.cgi?id=18845 Ethan Watson changed: What|Removed |Added CC||goober...@gmail.com ---

[Issue 18845] Extern(C++) class with no virtual functions

https://issues.dlang.org/show_bug.cgi?id=18845 Manu changed: What|Removed |Added Keywords||C++ --

[Issue 18845] New: Extern(C++) class with no virtual functions

https://issues.dlang.org/show_bug.cgi?id=18845 Issue ID: 18845 Summary: Extern(C++) class with no virtual functions Product: D Version: D2 Hardware: All OS: All Status: NEW Severity: enhancement

Re: Extra .tupleof field in structs with disabled postblit blocks non-GC-allocation trait

On Wednesday, 9 May 2018 at 18:04:40 UTC, Per Nordlöw wrote: On Wednesday, 9 May 2018 at 17:52:48 UTC, Meta wrote: I wasn't able to reproduce it on dmd-nightly: https://run.dlang.io/is/9wT8tH What version of the compiler are you using? Ahh, the struct needs to be in a unittest block for it

Re: Why The D Style constants are written in camelCase?

On Wednesday, 9 May 2018 at 15:20:12 UTC, Jonathan M Davis wrote: On Wednesday, May 09, 2018 14:12:41 Dmitry Olshansky via Digitalmars-d-learn wrote: [...] To an extent that's true, but anyone providing a library for use by others in the D community should seriously consider following it

Re: Need help with the dmd package on NixOS

On Friday, 4 May 2018 at 20:27:33 UTC, Thomas Mader wrote: The dmd package on NixOS doesn't work anymore in their master branch. Since dmd still works correctly on the stable branch I tried to examine the differences of libphobos2.a. I switched back to version 2.079.0 on master to have the

Re: Binderoo additional language support?

On Monday, 7 May 2018 at 17:28:55 UTC, Ethan wrote: 13 responses so far. Cheers to those 13. 4 responses since that post. And all four have listed "Plain old ordinary C" as something they want supported. Classic. Now it's in front of every other option. Supporting C is step one to

Re: Binderoo additional language support?

On Tuesday, 8 May 2018 at 14:28:53 UTC, jmh530 wrote: I don't really understand what to use binderoo for. So rather than fill out the questionnaire, maybe I would just recommend you do some work on wiki, blog post, or simple examples. Been putting that off until the initial proper stable

Re: Simple web server benchmark - vibe.d is slower than node.js and Go?

On Monday, 30 October 2017 at 17:23:02 UTC, Daniel Kozak wrote: Maybe this one: import vibe.d; import std.regex; import std.array : appender; static reg = ctRegex!"^/greeting/([a-z]+)$"; void main() { setupWorkerThreads(logicalProcessorCount); runWorkerTaskDist();

Re: unit-threaded v0.7.45 - now with more fluency

On 2018-05-08 09:07, Nick Sabalausky (Abscissa) wrote: The question is: Why "should.equal" instead of "shouldEqual"? The dot only seems there to be cute. It scales better. This way only one "should" function is needed and one "not" function. Otherwise there would be a lot of duplication,

Re: "Start a Minimal web server" example do not work.

On 08/05/2018 21:36, BoQsc wrote: On Tuesday, 8 May 2018 at 19:19:26 UTC, Seb wrote: On Tuesday, 8 May 2018 at 18:40:34 UTC, BoQsc wrote: On Tuesday, 8 May 2018 at 18:38:10 UTC, BoQsc wrote: On Tuesday, 8 May 2018 at 17:35:13 UTC, Jesse Phillips wrote: [...] Tested with these versions so

Re: Extra .tupleof field in structs with disabled postblit blocks non-GC-allocation trait

On Wednesday, 9 May 2018 at 17:52:48 UTC, Meta wrote: I wasn't able to reproduce it on dmd-nightly: https://run.dlang.io/is/9wT8tH What version of the compiler are you using? Ahh, the struct needs to be in a unittest block for it to happen: struct R { @disable this(this); int* _ptr;

Re: Extra .tupleof field in structs with disabled postblit blocks non-GC-allocation trait

On Wednesday, 9 May 2018 at 14:07:37 UTC, Per Nordlöw wrote: Why (on earth) does struct S { @disable this(this); int* _ptr; } pragma(msg, typeof(S.tupleof)); prints (int*, void*) when struct S { int* _ptr; } pragma(msg,

[Issue 18121] Needleless findSplit* methods

https://issues.dlang.org/show_bug.cgi?id=18121 --- Comment #1 from hst...@quickfur.ath.cx --- Found a similar need for needleless overloads of findSplit* today too. The context is that I'm trying to tokenize a string, and if it starts with a digit, say "1234abcd" I'd like to be able to split it

[Issue 18121] Needleless findSplit* methods

https://issues.dlang.org/show_bug.cgi?id=18121 hst...@quickfur.ath.cx changed: What|Removed |Added CC||hst...@quickfur.ath.cx --

Re: Wait-free MPSC and MPMC implement in D

On Wednesday, May 09, 2018 07:13:08 Shachar Shemesh via Digitalmars-d wrote: > I have a motto in life - if you assume you're great, you most likely > aren't. I have grown out of the "my code has no bugs" phase of my life > quite a while ago. The scary truth is that no matter what you do, you're

Re: Documentation for assumeUnique

On Tuesday, 8 May 2018 at 14:35:15 UTC, Seb wrote: On Monday, 7 May 2018 at 15:32:56 UTC, bachmeier wrote: You can see the messed up documentation here: https://dlang.org/library/std/exception/assume_unique.html Fix: https://github.com/dlang/dlang.org/pull/2364 Nice. Note: The

Re: dxml behavior after exception: continue parsing

On Tuesday, May 08, 2018 16:18:40 Jesse Phillips via Digitalmars-d-learn wrote: > On Monday, 7 May 2018 at 22:24:25 UTC, Jonathan M Davis wrote: > > I've been considering adding more configuration options where > > you say something like you don't care if any invalid characters > > are

Re: Bugzilla & PR sprint on the first weekend of every month

On Tuesday, 8 May 2018 at 18:48:15 UTC, Seb wrote: What do you guys think about having a dedicated "Bugzilla & PR sprint" at the first weekend of very month? We could organize this a bit by posting the currently "hot" bugs a few days ahead and also make sure that there are plenty of

Re: sumtype 0.3.0

On Wednesday, 9 May 2018 at 14:56:20 UTC, Paul Backus wrote: [snip] What length actually does, after all the compile-time stuff is expanded, is essentially this: switch(v.tag) { case 0: return sqrt(v.value!Rectangular.x**2 + v.value!Rectangular.y**2); case 1: return

Re: Why The D Style constants are written in camelCase?

On Wednesday, May 09, 2018 14:12:41 Dmitry Olshansky via Digitalmars-d-learn wrote: > On Wednesday, 9 May 2018 at 09:38:14 UTC, BoQsc wrote: > > The D Style suggest to camelCase constants, while Java naming > > conventions always promoted uppercase letter. > > > > Is there an explanation why D

Re: auto: useful, annoying or bad practice?

On Wednesday, May 09, 2018 14:31:00 Jesse Phillips via Digitalmars-d wrote: > On Wednesday, 9 May 2018 at 13:22:56 UTC, bauss wrote: > > Using "auto" you can also have multiple return types. > > > > auto foo(T)(T value) > > { > > > > static if (is(T == int)) return "int: " ~ to!string(value);

Re: sumtype 0.3.0

On Wednesday, 9 May 2018 at 13:33:44 UTC, jmh530 wrote: On Sunday, 6 May 2018 at 19:18:02 UTC, Paul Backus wrote: [snip] - Zero runtime overhead compared to hand-written C Just to clarify, would the run-time performance of the length function in the example be equivalent to if it had been

Re: Extra .tupleof field in structs with disabled postblit blocks non-GC-allocation trait

On Wednesday, 9 May 2018 at 14:36:38 UTC, Per Nordlöw wrote: On Wednesday, 9 May 2018 at 14:34:02 UTC, Per Nordlöw wrote: On Wednesday, 9 May 2018 at 14:20:41 UTC, Per Nordlöw wrote: If so, we can temporarily modify the trait to exclude the last `void*` member of the `S.tuple`. Given that it's

Re: serialport v1.0.0

On Sunday, 6 May 2018 at 22:02:05 UTC, Oleg B wrote: Stable version of serialport package * Blocking `SerialPortBlk` for classic usage * Non-blocking `SerialPortNonBlk` and `SerialPortFR` for usage in fibers or in vibe-d * Variative initialization and configuration * Hardware flow control

Re: Extra .tupleof field in structs with disabled postblit blocks non-GC-allocation trait

On Wednesday, 9 May 2018 at 14:34:02 UTC, Per Nordlöw wrote: On Wednesday, 9 May 2018 at 14:20:41 UTC, Per Nordlöw wrote: If so, we can temporarily modify the trait to exclude the last `void*` member of the `S.tuple`. Given that it's always added as the last member. Also note that

Re: auto: useful, annoying or bad practice?

On Wednesday, 9 May 2018 at 13:22:56 UTC, bauss wrote: Using "auto" you can also have multiple return types. auto foo(T)(T value) { static if (is(T == int)) return "int: " ~ to!string(value); else return value; } You cannot give that function a specific return type as it's either T or

Re: Extra .tupleof field in structs with disabled postblit blocks non-GC-allocation trait

On Wednesday, 9 May 2018 at 14:20:41 UTC, Per Nordlöw wrote: If so, we can temporarily modify the trait to exclude the last `void*` member of the `S.tuple`. Given that it's always added as the last member. Also note that pragma(msg, __traits(isDisabled, S.this(this))); fails to compile

Re: Extra .tupleof field in structs with disabled postblit blocks non-GC-allocation trait

On Wednesday, 9 May 2018 at 14:20:41 UTC, Per Nordlöw wrote: If so, we can temporarily modify the trait to exclude the last `void*` member of the `S.tuple`. Given that it's always added as the last member. Note that `std.traits.isCopyable!S` cannot be used, because it will return true when

Re: Extra .tupleof field in structs with disabled postblit blocks non-GC-allocation trait

On Wednesday, 9 May 2018 at 14:07:37 UTC, Per Nordlöw wrote: This prevents the trait `mustAddGCRangeOfStructOrUnion` [1] from detecting when a container with manual memory management doesn't have to be scanned by the GC as in, for instance, enum NoGc; struct S { @disable

Re: Why The D Style constants are written in camelCase?

On Wednesday, 9 May 2018 at 09:38:14 UTC, BoQsc wrote: The D Style suggest to camelCase constants, while Java naming conventions always promoted uppercase letter. Is there an explanation why D Style chose to use camelCase instead of all UPPERCASE for constants, was there any technical

Extra .tupleof field in structs with disabled postblit blocks non-GC-allocation trait

Why (on earth) does struct S { @disable this(this); int* _ptr; } pragma(msg, typeof(S.tupleof)); prints (int*, void*) when struct S { int* _ptr; } pragma(msg, typeof(S.tupleof)); prints (int*) ?!!! This prevents the trait

Re: sumtype 0.3.0

On Sunday, 6 May 2018 at 19:18:02 UTC, Paul Backus wrote: [snip] - Zero runtime overhead compared to hand-written C Just to clarify, would the run-time performance of the length function in the example be equivalent to if it had been specialized for the Rectangular types (e.g. double

Re: auto: useful, annoying or bad practice?

On Wednesday, 9 May 2018 at 12:44:34 UTC, Jonathan M Davis wrote: On Monday, April 30, 2018 21:11:07 Gerald via Digitalmars-d wrote: [...] I think that the overall consensus is that it's great but that you do have to be careful about using it when it reduces clarity without adding other

Re: sumtype 0.3.0

On Monday, 7 May 2018 at 21:35:44 UTC, Paul Backus wrote: On Monday, 7 May 2018 at 19:28:16 UTC, Sönke Ludwig wrote: Another similar project: http://taggedalgebraic.dub.pm/ There's also tagged_union and minivariant on dub, that I've found. I'm definitely far from the first person to be

Re: auto: useful, annoying or bad practice?

On Monday, April 30, 2018 21:11:07 Gerald via Digitalmars-d wrote: > I'll freely admit I haven't put a ton of thought into this post > (never a good start), however I'm genuinely curious what people's > feeling are with regards to the auto keyword. > > Speaking for myself, I dislike the auto

Re: Generating a method using a UDA

On Wednesday, 9 May 2018 at 10:16:22 UTC, Melvin wrote: I'm trying to find a friendly syntax for defining things in a framework. For context, I've been looking into finding a solution for this problem (https://github.com/GodotNativeTools/godot-d/issues/1) on the Godot-D project. I've done

Re: Generating a method using a UDA

On Wednesday, 9 May 2018 at 10:16:22 UTC, Melvin wrote: class SomeNode : GodotScript!Node { @Signal void testSignal(float a, long b); // The declaration above would trigger the generation of this line void testSignal(float a, long b) { owner.emitSignal("testSignal", a, b); }

Re: Why The D Style constants are written in camelCase?

On Wednesday, May 09, 2018 09:38:14 BoQsc via Digitalmars-d-learn wrote: > The D Style suggest to camelCase constants, while Java naming > conventions always promoted uppercase letter. > > Is there an explanation why D Style chose to use camelCase > instead of all UPPERCASE for constants, was

Re: unit-threaded v0.7.45 - now with more fluency

On Wednesday, 9 May 2018 at 10:37:52 UTC, Cym13 wrote: On Wednesday, 9 May 2018 at 04:40:37 UTC, Nick Sabalausky (Abscissa) wrote: On 05/08/2018 05:05 AM, Cym13 wrote: [...] No, it really doesn't mean the same thing at all. Not when you look away from the unimportant implementation details

Re: Geany editor: Dlang code autocomplete

On Tuesday, 8 May 2018 at 22:27:19 UTC, Alexibu wrote: On Tuesday, 8 May 2018 at 07:47:26 UTC, Denis Feklushkin wrote: Hi! Does anyone else use Geany as Dlang code editor? I use Geany for D. It already performs autocomplete. I am not sure how good it is. It isn't something I'm that

[Issue 18844] std.utf.decode skips valid character on invalid multibyte sequence

https://issues.dlang.org/show_bug.cgi?id=18844 --- Comment #1 from FeepingCreature --- Repro: string s = cast(string) [cast(ubyte) 'ä', 't']; size_t i = 0; auto ch = decode!(UseReplacementDchar.yes, string)(s, i); writefln("ch = %s, i = %s, should be

[Issue 18844] New: std.utf.decode skips valid character on invalid multibyte sequence

https://issues.dlang.org/show_bug.cgi?id=18844 Issue ID: 18844 Summary: std.utf.decode skips valid character on invalid multibyte sequence Product: D Version: D2 Hardware: x86_64 OS: Linux Status:

Re: unit-threaded v0.7.45 - now with more fluency

On Wednesday, 9 May 2018 at 04:40:37 UTC, Nick Sabalausky (Abscissa) wrote: On 05/08/2018 05:05 AM, Cym13 wrote: [...] No, it really doesn't mean the same thing at all. Not when you look away from the unimportant implementation details and towards the big picture: [...] With UFCS I find

Generating a method using a UDA

I'm trying to find a friendly syntax for defining things in a framework. For context, I've been looking into finding a solution for this problem (https://github.com/GodotNativeTools/godot-d/issues/1) on the Godot-D project. I've done some investigating already, and it looks like I can only

Re: Why The D Style constants are written in camelCase?

On Wednesday, 9 May 2018 at 09:38:14 UTC, BoQsc wrote: The D Style suggest to camelCase constants, while Java naming conventions always promoted uppercase letter. Is there an explanation why D Style chose to use camelCase instead of all UPPERCASE for constants, was there any technical

Re: Why The D Style constants are written in camelCase?

On Wednesday, 9 May 2018 at 09:51:37 UTC, bauss wrote: Just because. To add on to this. D is not Java, it's not C++, it's not C# etc. D is D and D has its own conventions. You're free to write your constants in all uppercase if you want. I guess if I should come up with an actual reason

Re: Geany editor: Dlang code autocomplete

On Wednesday, 9 May 2018 at 09:44:07 UTC, Basile B. wrote: On Wednesday, 9 May 2018 at 08:48:41 UTC, Denis Feklushkin wrote: On Tuesday, 8 May 2018 at 22:52:26 UTC, Basile B. wrote: On Tuesday, 8 May 2018 at 07:47:26 UTC, Denis Feklushkin wrote: Unlike it, we have almost everything ready:

Re: Geany editor: Dlang code autocomplete

On Wednesday, 9 May 2018 at 08:48:41 UTC, Denis Feklushkin wrote: On Tuesday, 8 May 2018 at 22:52:26 UTC, Basile B. wrote: On Tuesday, 8 May 2018 at 07:47:26 UTC, Denis Feklushkin wrote: Unlike it, we have almost everything ready: https://github.com/denizzzka/geany_dlang Hello have a

Why The D Style constants are written in camelCase?

The D Style suggest to camelCase constants, while Java naming conventions always promoted uppercase letter. Is there an explanation why D Style chose to use camelCase instead of all UPPERCASE for constants, was there any technical problem that would appear while writing in all UPPERCASE?

Re: Geany editor: Dlang code autocomplete

On Tuesday, 8 May 2018 at 19:23:44 UTC, Seb wrote: On Tuesday, 8 May 2018 at 07:47:26 UTC, Denis Feklushkin wrote: Hi! Does anyone else use Geany as Dlang code editor? I'm looking at the ongoing fundraising for another editor. Unlike it, we have almost everything ready:

Re: Geany editor: Dlang code autocomplete

On Tuesday, 8 May 2018 at 22:27:19 UTC, Alexibu wrote: On Tuesday, 8 May 2018 at 07:47:26 UTC, Denis Feklushkin wrote: Hi! Does anyone else use Geany as Dlang code editor? I use Geany for D. It already performs autocomplete. I am not sure how good it is. dcd does this job better than

Re: unit-threaded v0.7.45 - now with more fluency

On Saturday, 5 May 2018 at 15:51:11 UTC, Johannes Loher wrote: On Saturday, 5 May 2018 at 13:28:41 UTC, Atila Neves wrote: For those not in the know, unit-threaded is an advanced testing library for D that runs tests in threads by default. It has a lot of features:

Re: Geany editor: Dlang code autocomplete

On Tuesday, 8 May 2018 at 22:52:26 UTC, Basile B. wrote: On Tuesday, 8 May 2018 at 07:47:26 UTC, Denis Feklushkin wrote: Unlike it, we have almost everything ready: https://github.com/denizzzka/geany_dlang Hello have a look here: https://github.com/denizzzka/geany_dlang. I cant tell if

Re: Wait-free MPSC and MPMC implement in D

On Wednesday, 9 May 2018 at 04:13:08 UTC, Shachar Shemesh wrote: On 09/05/18 03:20, Andy Smith wrote: [...] Let me start off by saying that it is great that people appreciate and enjoy Mecca. With that said, I would be wary of the direction this thread is threatening to take. [...] Well

[Issue 18828] [-betterC] helpless error in object.d

https://issues.dlang.org/show_bug.cgi?id=18828 --- Comment #9 from Mike Franklin --- A feeble attempt at a fix https://github.com/dlang/druntime/pull/2178 --

[Issue 15388] extern(C++) - typeof(null) should mangle as nullptr_t

https://issues.dlang.org/show_bug.cgi?id=15388 github-bugzi...@puremagic.com changed: What|Removed |Added Status|NEW |RESOLVED

[Issue 15388] extern(C++) - typeof(null) should mangle as nullptr_t

https://issues.dlang.org/show_bug.cgi?id=15388 --- Comment #3 from github-bugzi...@puremagic.com --- Commit pushed to master at https://github.com/dlang/dmd https://github.com/dlang/dmd/commit/c38ae836e3ab171a0d543fb3eaf7ff94b199cee4 Fix issue 15388 - extern(C++) - typeof(null) should mangle as