Re: DCompute is now in the master branch of LDC

On 1 June 2017 at 09:28, Nicholas Wilson via Digitalmars-d-announce < digitalmars-d-announce@puremagic.com> wrote: > On Wednesday, 31 May 2017 at 22:15:33 UTC, Wulfklaue wrote: > >> >> And so what if people start a big discussion about the name. If only 10% >> of those people come to the D site

Re: DCompute is now in the master branch of LDC

On 31 May 2017 at 05:32, H. S. Teoh via Digitalmars-d-announce < digitalmars-d-announce@puremagic.com> wrote: > On Tue, May 30, 2017 at 07:23:42PM +, Jack Stouffer via > Digitalmars-d-announce wrote: > > On Tuesday, 30 May 2017 at 18:06:56 UTC, Walter Bright wrote: > > > I fear the

Re: DCompute is now in the master branch of LDC

On 31 May 2017 at 04:06, Walter Bright via Digitalmars-d-announce < digitalmars-d-announce@puremagic.com> wrote: > On 5/30/2017 5:12 AM, Nicholas Wilson wrote: > >> Ah, isn't English wonderful. I guess Walter is suffering the inverse of >> the Calvin & Hobbes "Verbing nouns weirds the language",

Re: Isn't it about time for D3?

On Tuesday, 13 June 2017 at 17:57:14 UTC, Patrick Schluter wrote: Before even contemplating a big disrupting language split like proposed by the OP, wouldn't it first more appropriate to write a nice article, DIP, blog, whatever, listing the defects of the current language that can not be

Re: dmd: why not use fully qualified names for types in error messages?

On Tue, Jun 13, 2017 at 09:50:29PM -0700, Timothee Cour via Digitalmars-d wrote: > eg: > Error: no property 'IF_gray' for type 'ImageFormat' > => > Error: no property 'IF_gray' for type 'foo.bar.ImageFormat' I support such a change. Is there an issue filed in bugzilla for this? I'd add that

[your code here]

Please send a code

dmd: why not use fully qualified names for types in error messages?

eg: Error: no property 'IF_gray' for type 'ImageFormat' => Error: no property 'IF_gray' for type 'foo.bar.ImageFormat' and also, why not show where the symbol is defined? would PR's for that be accepted? is that hard to implement?

Re: D now available on Codefights.com

Very cool I've never heard of codefights.com before but I'm giving it as try right now (with D, of course) and I'm really enjoying it! :) Kudos to all involved!! :)

Re: foreach range with index

On Wednesday, 14 June 2017 at 03:06:26 UTC, Luís Marques wrote: On Wednesday, 14 June 2017 at 02:54:30 UTC, 9il wrote: Random access iteration is more expensive then front/popFront in general case. For arrays it is not true. But for many other kinds of ranges it is. For example ranges that do

Re: foreach range with index

On Wednesday, 14 June 2017 at 02:54:30 UTC, 9il wrote: Random access iteration is more expensive then front/popFront in general case. For arrays it is not true. But for many other kinds of ranges it is. For example ranges that do not have contiguous memory representation (strided vectors,

Re: foreach range with index

On Wednesday, 14 June 2017 at 02:48:34 UTC, Luís Marques wrote: Hmm, I suppose that even if we have all of the good stuff of length, opIndex, opSlice, etc., we can't assume the indices are [0..length], right? But there should be some way for, say, map to preserve that information from the

Re: foreach range with index

On Wednesday, 14 June 2017 at 02:42:46 UTC, Luís Marques wrote: On Tuesday, 13 June 2017 at 21:44:43 UTC, Steven Schveighoffer wrote: But I think leaving the definition of the index up to the range itself is paramount -- I don't want every range to be able to have a size_t index, as that's not

Re: foreach range with index

On Wednesday, 14 June 2017 at 02:42:46 UTC, Luís Marques wrote: On Tuesday, 13 June 2017 at 21:44:43 UTC, Steven Schveighoffer wrote: But I think leaving the definition of the index up to the range itself is paramount -- I don't want every range to be able to have a size_t index, as that's not

Re: foreach range with index

On Tuesday, 13 June 2017 at 21:44:43 UTC, Steven Schveighoffer wrote: But I think leaving the definition of the index up to the range itself is paramount -- I don't want every range to be able to have a size_t index, as that's not always what you want, and it conflicts with other items. What

Re: CTFE Status 2

On Thursday, 16 February 2017 at 21:05:51 UTC, Stefan Koch wrote: [ ... ] Slice Assignment bugs fixed! With that we are green again. I am going to improve concat a little such that it computes the buffer lengths if it can. And allocs the needed amount upfront. The alternative is lazy

Re: Generic operator overloading for immutable types?

On 6/13/17 7:51 PM, ag0aep6g wrote: On 06/14/2017 12:45 AM, Steven Schveighoffer wrote: No, the fact that immutable implicitly casts to const(inout) is a special property enabled by the knowledge that immutable data can NEVER change, so it's OK to assume it's (at least) const for all

D now available on Codefights.com

Hey, The site https://codefights.com is a place to test and improve your programming skills. The challenges include interview-type problems, shortest code contests, duels with other coders, monthly tournaments, and more. If you perform well, you can opt in to get connected with partner

[Issue 17117] [REG2.073] erroneous "escaping reference to local variable"

https://issues.dlang.org/show_bug.cgi?id=17117 --- Comment #9 from Martin Krejcirik --- FYI this was fixed by https://github.com/dlang/dmd/pull/6420 --

Re: Generic operator overloading for immutable types?

On 06/14/2017 12:45 AM, Steven Schveighoffer wrote: No, the fact that immutable implicitly casts to const(inout) is a special property enabled by the knowledge that immutable data can NEVER change, so it's OK to assume it's (at least) const for all references. The same cannot be true of const

[Issue 17500] New: Add a CLI flag configure the location for AST dumps produced by -vcg-ast

https://issues.dlang.org/show_bug.cgi?id=17500 Issue ID: 17500 Summary: Add a CLI flag configure the location for AST dumps produced by -vcg-ast Product: D Version: D2 Hardware: x86_64 OS: Linux

Re: Static Initialization of Struct as UDA

On Tuesday, 13 June 2017 at 22:16:37 UTC, ag0aep6g wrote: No bug. `static` has no effect on module-level variables. `z` is a normal mutable variable, not at all guaranteed to be constant. Make it an `enum` or `immutable`. Note that immutable doesn't guarantee compile-time constancy,

Re: Generic operator overloading for immutable types?

On 6/13/17 5:58 PM, ag0aep6g wrote: On 06/13/2017 10:50 PM, Steven Schveighoffer wrote: const(inout) actually *is* a thing :) It's a type constructor that can be implicitly cast from immutable. This has advantages in some cases. See (horribly written) table at the bottom if the inout function

Re: Static Initialization of Struct as UDA

On 06/14/2017 12:04 AM, jmh530 wrote: The code below doesn't compile because "static variable z cannot be read at compile time". However, z is a static variable, so I don't see why it wouldn't be available at compile-time. Bug or am I missing something? struct Bar { int x = 2; int

Re: Static Initialization of Struct as UDA

On Tuesday, 13 June 2017 at 22:04:48 UTC, jmh530 wrote: The code below doesn't compile because "static variable z cannot be read at compile time". However, z is a static variable, so I don't see why it wouldn't be available at compile-time. Bug or am I missing something? struct Bar {

Static Initialization of Struct as UDA

The code below doesn't compile because "static variable z cannot be read at compile time". However, z is a static variable, so I don't see why it wouldn't be available at compile-time. Bug or am I missing something? struct Bar { int x = 2; int y; } static Bar z = {y:1}; void main()

Re: Generic operator overloading for immutable types?

On 06/13/2017 10:50 PM, Steven Schveighoffer wrote: const(inout) actually *is* a thing :) It's a type constructor that can be implicitly cast from immutable. This has advantages in some cases. See (horribly written) table at the bottom if the inout function section here:

Re: Getters/setters generator

On Tuesday, 13 June 2017 at 20:45:34 UTC, jmh530 wrote: Fair point. I just was playing around with it today and was like, oh that's pretty easy. It was only when I was trying to see if anyone else had done anything like this that I came across your project. I was just looking at the code

Re: foreach range with index

On 6/13/17 1:15 PM, Luís Marques wrote: In the documentation for foreach with range concepts (not x..y ranges) () I did not find anything about foreach supporting iteration indices/tuple unpacking for ranges, such as `foreach(i, elm;

[Issue 9817] Syntax change for front tuple expansion in foreach

https://issues.dlang.org/show_bug.cgi?id=9817 Steven Schveighoffer changed: What|Removed |Added Status|NEW |RESOLVED

Re: LDC 1.3.0-beta2

On Tuesday, 13 June 2017 at 16:29:24 UTC, Luís Marques wrote: I look forward to LDC using the current frontend: I had to revert my use of -dip1000 because LDC 1.3.0-beta2 complains about Phobos errors when used with that option. 2.074.1 integration is as good as complete; you may build

Re: Makefile experts, unite!

Ralph Amissah wrote: On Sun, Jun 11 2017, Jonathan M Davis via Digitalmars-d wrote: And where do existing D build systems fit into the picture, I seem to recall this general discussion around the announcement of "button", which seems interesting, potentially

Re: First time user of LDC and getting newbie problems.

On Tuesday, 13 June 2017 at 20:04:46 UTC, WhatMeWorry wrote: Sorry I didn't reply sooner. I just reinstalled everything and it's all good. Something was really screwed up. "Screwed up" is also a fairly good way to describe my responses too, since I also missed your clear statement that you

Re: Isn't it about time for D3?

crimaniak wrote: If it depended on me, I would declare an embargo on language changes that's why we (me, and others like me ;-) need D3. i don't need "better phobos", for example ('cause i'm trying to aboid using phobos anyway), but i really need named arguments (`foo(a:42, b:"hello")`). i

Re: Isn't it about time for D3?

Patrick Schluter wrote: Before even contemplating a big disrupting language split like proposed by the OP, wouldn't it first more appropriate to write a nice article, DIP, blog, whatever, listing the defects of the current language that can not be solved by progressive evolution? I haven't

Re: Generic operator overloading for immutable types?

On 6/13/17 3:58 PM, ag0aep6g wrote: On 06/13/2017 09:29 PM, Gary Willoughby wrote: Is it possible for the `result` variable in the following code to be returned as an immutable type if it's created by adding two immutable types? Qualify the return type as `inout`: inout(Rational)

Re: Getters/setters generator

On Tuesday, 13 June 2017 at 20:31:25 UTC, Eugene Wissner wrote: I suppose the errors will be more cryptic, since you don't check if the string referers to an existing member. You provide only get/set that return by value. So you may need to generate getters/setters for const values, for ref

Re: Isn't it about time for D3?

jmh530 wrote: Nevertheless, C++ is still a constantly evolving language. one of the key features of evolution is removing old and rudimentary things. without this, it is not evolution, it is mutilation...

Re: Getters/setters generator

On Tuesday, 13 June 2017 at 19:31:28 UTC, jmh530 wrote: On Sunday, 11 December 2016 at 02:17:18 UTC, Mike Parker wrote: What are properties if not "getters" and "setters"? From the original post: "It would generate 2 methods "num": one to set num_ and one to get its value." Two methods

Re: First time user of LDC and getting newbie problems.

On Tuesday, 13 June 2017 at 12:39:53 UTC, Joseph Rushton Wakeling wrote: On Tuesday, 13 June 2017 at 12:38:03 UTC, Joseph Rushton Wakeling wrote: On Sunday, 11 June 2017 at 21:58:27 UTC, WhatMeForget wrote: Just trying to compile a "Hello World" using dub and ldc2. I presume from your

Re: Generic operator overloading for immutable types?

On 06/13/2017 09:29 PM, Gary Willoughby wrote: Is it possible for the `result` variable in the following code to be returned as an immutable type if it's created by adding two immutable types? Qualify the return type as `inout`: inout(Rational) opBinary(/*...*/)(/*...*/) inout {/*...*/}

Re: Isn't it about time for D3?

On Tuesday, 13 June 2017 at 17:57:14 UTC, Patrick Schluter wrote: I haven't the impression that the *language* itself suffer from so big flaws that it would warrant to fork it in a way that will lead to a lot frustration and bewilderment. I have the same opinion. Raw libraries, poor

Re: Getters/setters generator

On Sunday, 11 December 2016 at 02:17:18 UTC, Mike Parker wrote: What are properties if not "getters" and "setters"? From the original post: "It would generate 2 methods "num": one to set num_ and one to get its value." Two methods named "num". No "get" or "set" in sight. Sorry to bump,

Re: Generic operator overloading for immutable types?

On Tuesday, 13 June 2017 at 11:36:45 UTC, Steven Schveighoffer wrote: Nope, const works just fine. A clue is in your return type -- it's not inout! This should work: public Rational opBinary(string op)(Rational rhs) const If Rational had any indirections, then inout would be required, and

[Issue 17499] New: with -betterC switch, call C's assert failure function rather than druntime's

https://issues.dlang.org/show_bug.cgi?id=17499 Issue ID: 17499 Summary: with -betterC switch, call C's assert failure function rather than druntime's Product: D Version: D2 Hardware: All OS: All

[Issue 17498] Double error message about use of private

https://issues.dlang.org/show_bug.cgi?id=17498 Eyal changed: What|Removed |Added Keywords||diagnostic --

[Issue 17498] New: Double error message about use of private

https://issues.dlang.org/show_bug.cgi?id=17498 Issue ID: 17498 Summary: Double error message about use of private Product: D Version: D2 Hardware: All OS: All Status: NEW Severity: trivial

Re: How to implement opCmp?

On Tuesday, 13 June 2017 at 16:49:14 UTC, H. S. Teoh wrote: On Tue, Jun 13, 2017 at 10:51:40AM -0400, Steven Schveighoffer via Digitalmars-d-learn wrote: [...] I think Andrei has a nice way to do opCmp for integers that's a simple subtraction and negation or something like that. [...] In

Re: Makefile experts, unite!

On Sun, Jun 11 2017, Jonathan M Davis via Digitalmars-d wrote: And where do existing D build systems fit into the picture, I seem to recall this general discussion around the announcement of "button", which seems interesting, potentially awesome even: Button

Re: How to implement opCmp?

On Tuesday, 13 June 2017 at 14:51:40 UTC, Steven Schveighoffer wrote: Yes, I saw that when I was looking (you can see from my reply that you quoted below). Yes, I had missed that point. Yes I think it makes sense to have such a comparison function for non-ranges. Yes it probably belongs

Re: Isn't it about time for D3?

Before even contemplating a big disrupting language split like proposed by the OP, wouldn't it first more appropriate to write a nice article, DIP, blog, whatever, listing the defects of the current language that can not be solved by progressive evolution? I haven't the impression that the

foreach range with index

In the documentation for foreach with range concepts (not x..y ranges) () I did not find anything about foreach supporting iteration indices/tuple unpacking for ranges, such as `foreach(i, elm; range)`. It is "documented" in an example

Re: How to implement opCmp?

On Tue, Jun 13, 2017 at 10:51:40AM -0400, Steven Schveighoffer via Digitalmars-d-learn wrote: [...] > I think Andrei has a nice way to do opCmp for integers that's a simple > subtraction and negation or something like that. [...] In theory, cmp(int x, int y) can be implemented simply as (x - y).

Re: Supporting musl libc

On Tuesday, 13 June 2017 at 10:10:38 UTC, Joseph Rushton Wakeling wrote: On Tuesday, 13 June 2017 at 09:42:43 UTC, Joakim wrote: Also, it's possible others are still adding Glibc stuff as just linux, as that's happened a couple times since then, but I don't follow it and tell them to change

Re: LDC 1.3.0-beta2

On Monday, 12 June 2017 at 17:49:46 UTC, kinke wrote: This release is based on the 2.073.2 frontend and standard library and supports LLVM 3.5-4.0. Nice job. I look forward to LDC using the current frontend: I had to revert my use of -dip1000 because LDC 1.3.0-beta2 complains about Phobos

Re: "Programming in D" is up-to-date

On Saturday, 10 June 2017 at 23:20:43 UTC, Ali Çehreli wrote: On 06/10/2017 12:53 PM, adamss3 wrote: I just got the paper back which has been upgraded to the latest version. I'm wondering if the hardcover version has been upgraded as well. There is no way of knowing for sure but from my

Re: atomic operations compared to c++

LDC uses seq_cst seq_cst

Re: Isn't it about time for D3?

On Tuesday, 13 June 2017 at 13:29:45 UTC, jmh530 wrote: Companies clearly value C++'s backwards compatibility. However, if there's one lesson from the D1/D2 or the Python 2/Python 3 split, it's that it's hugely disruptive (so much so that I find The D1/D2 split was actually a unifier. It was

Re: How to implement opCmp?

On 6/11/17 11:24 AM, Honey wrote: On Friday, 9 June 2017 at 17:50:28 UTC, Honey wrote: Looking at the implementation of Tuple.opCmp, I'm not sure I'd bet on existence of opCmp for fundamental types: int opCmp(R)(R rhs) if (areCompatibleTuples!(typeof(this), R, "<")) {

Berlin D Meetup June 2017

Hi All, The Berlin June D meetup is happening on this Friday the 16th at 19:30 at Berlin Co-Op (http://co-up.de/) on the fifth floor. Mathias Lang will be giving a short talk on metaprogramming tricks in D. In particular on a "Self generating visitor pattern and a safe and correct tagged

Re: Isn't it about time for D3?

On Tuesday, 13 June 2017 at 12:23:19 UTC, ketmar wrote: Sebastien Alaiwan wrote: My point precisely was that "not splitting D1/D2" might correspond to "doing things right". "not splitting" here means "we're stuck with D1". deprecation cycle of several years (not counting the time required

Re: The DLang Tour translated into Russian

On Saturday, 10 June 2017 at 17:20:14 UTC, Stanislav Blinov wrote: Hi everyone! We're happy to announce that as of today, the Russian translation of the DLang Tour chapters is available here: https://tour.dlang.org/tour/ru/welcome/welcome-to-d , and of course via the language selection page:

Re: Makefile experts, unite!

On Tuesday, 13 June 2017 at 06:05:16 UTC, Sebastien Alaiwan wrote: On Monday, 12 June 2017 at 15:57:13 UTC, Meta wrote: On Monday, 12 June 2017 at 06:34:31 UTC, Sebastien Alaiwan wrote: On Monday, 12 June 2017 at 06:30:16 UTC, ketmar wrote: Jonathan M Davis wrote: It's certainly a pain to

Re: LDC 1.3.0-beta2

On Tuesday, 13 June 2017 at 09:27:42 UTC, Oleg B wrote: You plain build armhf version, like for 1.1.0? Or will it never happen again? It will happen again I assume, but we don't have the capacity at the moment.

Re: First time user of LDC and getting newbie problems.

On Tuesday, 13 June 2017 at 12:38:03 UTC, Joseph Rushton Wakeling wrote: On Sunday, 11 June 2017 at 21:58:27 UTC, WhatMeForget wrote: Just trying to compile a "Hello World" using dub and ldc2. I presume from your command line you're running Windows? ... I don't know where I got that idea

Re: First time user of LDC and getting newbie problems.

On Sunday, 11 June 2017 at 21:58:27 UTC, WhatMeForget wrote: Just trying to compile a "Hello World" using dub and ldc2. Let's start from the beginning: how did you install LDC? I presume from your command line you're running Windows?

Re: Developer positions at Sociomantic Labs

On Tuesday, 13 June 2017 at 12:16:48 UTC, Vadim Lopatin wrote: Is German needed? No. The office is English-speaking (and very international).

Re: Isn't it about time for D3?

Sebastien Alaiwan wrote: My point precisely was that "not splitting D1/D2" might correspond to "doing things right". "not splitting" here means "we're stuck with D1". deprecation cycle of several years (not counting the time required to actually *start* the process) means "no evolution".

Re: Developer positions at Sociomantic Labs

On Tuesday, 13 June 2017 at 10:25:14 UTC, Joseph Rushton Wakeling wrote: On Tuesday, 13 June 2017 at 02:53:14 UTC, Dsby wrote: 唉、、My poor English、、、 English is important to us, but if you're keen, I would encourage you to apply anyway and let us make the decision on whether you're at the

Re: Isn't it about time for D3?

On Tuesday, 13 June 2017 at 06:56:14 UTC, ketmar wrote: Sebastien Alaiwan wrote: On Sunday, 11 June 2017 at 17:59:54 UTC, ketmar wrote: Guillaume Piolat wrote: On Saturday, 10 June 2017 at 23:30:18 UTC, Liam McGillivray wrote: I realize that there are people who want to continue using D as

Re: anyone using msgpackrpc-d ? it's currently broken and doesn't seem maintained

On Monday, 12 June 2017 at 18:12:38 UTC, Timothee Cour wrote: any help on this would be most welcome: https://github.com/msgpack-rpc/msgpack-rpc-d/issues/16 Unfortunately I find the RPC support in D lacking. Having a good RPC integration for D is key for production use of D where one wants

Re: Weird template instantiation problem

On 6/12/17 11:31 AM, Arafel wrote: As you can see, the only change is the type the function returns, but I don't see how it should make any difference. Also, changing from "enum" to "static immutable", or even removing the "enum" and directly embedding the function literal doesn't seem to make

Re: Generic operator overloading for immutable types?

On 6/12/17 3:36 PM, H. S. Teoh via Digitalmars-d-learn wrote: On Mon, Jun 12, 2017 at 07:38:44PM +, Gary Willoughby via Digitalmars-d-learn wrote: In the following code is there any way to make the `opBinary` method generic to be able to accept immutable as well as a standard type? The

Re: D, DStep, and Deimos

On 2017-06-13 13:22, Russel Winder via Digitalmars-d wrote: Having now got some bits of libdvbv5 usable from D with aid of DStep – which let's be honest did 90.357% (roughly) of the work – thoughts turn to maintenance and distribution. So a few questions/comments: 1. Is Deimos "alive and well"

Re: D, DStep, and Deimos

On 13/06/2017 12:22 PM, Russel Winder via Digitalmars-d wrote: Having now got some bits of libdvbv5 usable from D with aid of DStep – which let's be honest did 90.357% (roughly) of the work – thoughts turn to maintenance and distribution. So a few questions/comments: 1. Is Deimos "alive and

Re: Generic operator overloading for immutable types?

On 6/12/17 3:51 PM, Gary Willoughby wrote: I don't know how H. S. Teoh managed to answer 'before' I posted but thanks guys! :) D programmers are *that* good. Seriously though, for NNTP connections, timestamp is taken from the submitter's PC. -Steve

Re: D, DStep, and Deimos

On Tuesday, June 13, 2017 12:22:52 Russel Winder via Digitalmars-d wrote: > Having now got some bits of libdvbv5 usable from D with aid of DStep – > which let's be honest did 90.357% (roughly) of the work – thoughts turn > to maintenance and distribution. So a few questions/comments: > > 1. Is

D, DStep, and Deimos

Having now got some bits of libdvbv5 usable from D with aid of DStep – which let's be honest did 90.357% (roughly) of the work – thoughts turn to maintenance and distribution. So a few questions/comments: 1. Is Deimos "alive and well" as a place to host the current state of a D adaptor library,

Re: Developer positions at Sociomantic Labs

On Tuesday, 13 June 2017 at 02:53:14 UTC, Dsby wrote: 唉、、My poor English、、、 English is important to us, but if you're keen, I would encourage you to apply anyway and let us make the decision on whether you're at the level we need.

Re: Supporting musl libc

On Tuesday, 13 June 2017 at 09:42:43 UTC, Joakim wrote: Also, it's possible others are still adding Glibc stuff as just linux, as that's happened a couple times since then, but I don't follow it and tell them to change it, as it usually doesn't affect me on Android. If these are affecting

Re: Supporting musl libc

On Monday, 10 October 2016 at 15:19:00 UTC, Daniel Kozak wrote: Dne 10.10.2016 v 15:27 openwrt via Digitalmars-d napsal(a): On Sunday, 9 October 2016 at 15:48:49 UTC, Daniel Kozak wrote: On Sunday, 9 October 2016 at 13:38:33 UTC, Jacob Carlborg wrote: On 2016-10-08 20:47, Daniel Kozak wrote:

Re: LDC 1.3.0-beta2

On Monday, 12 June 2017 at 17:49:46 UTC, kinke wrote: Hi everyone, LDC 1.3.0-beta2, the LLVM-based D compiler, is available for download! This release is based on the 2.073.2 frontend and standard library and supports LLVM 3.5-4.0. It's been a while since beta1, so besides numerous fixes

Re: How to check whether a struct is templated?

On 06/13/2017 02:00 AM, Andre Pany wrote: I can not find a traits "isTemplateOf". You're close. :) https://dlang.org/phobos/std_traits.html#isInstanceOf Ali

Re: How to check whether a struct is templated?

Are you looking for something like this? import std.typecons; import std.traits; alias yes = Nullable!int; struct no {} template isNullable(T : Nullable!X, X) { enum isNullable = true; } template isNullable(T) { enum isNullable = false; } void main() { static

How to check whether a struct is templated?

Hi, I loop through a structure during compile time and want to check whether a field of the structure is of type Nullable. Therefore I use the TemplateOf traits which works for Nullable fields but raises an error for fields which are structures and not templated. static if(is(T == struct)

Lubeck: Hight Level Linear Algebra for Dlang

Hi I am pleased to announce the Lubeck [1] linear algebra library for Dlang. It is very easy to use and it has been tested in real world. See the dub project example [9] to start. libblas, libcblas, and liblapack should be installed and defined in user's DUB configuration. Alternatively,

Re: Makefile experts, unite!

On Mon, 2017-06-12 at 10:39 -0700, H. S. Teoh via Digitalmars-d wrote: > […] > Don't forget tup, and others inspired by it, which use modern OS > features to reduce the cost of determining what to build to an O(1) > database lookup rather than an O(n) whole-source tree scan. I.e., > much > faster

Re: Generic operator overloading for immutable types?

On Monday, 12 June 2017 at 20:10:17 UTC, H. S. Teoh wrote: Therefore, nowadays I always recommend writing parenthesis with type modifiers, so that the intent it unambiguous, i.e., always write `inout(Rational)` rather than `inout Rational`, unless you intend for `inout` to apply to the

[Issue 17497] New: [REG] OSX: tar.xz doesn't decompress correctly (from http://dlang.org/download.html)

https://issues.dlang.org/show_bug.cgi?id=17497 Issue ID: 17497 Summary: [REG] OSX: tar.xz doesn't decompress correctly (from http://dlang.org/download.html) Product: D Version: D2 Hardware: x86 OS: Mac OS X

[Issue 17495] __traits(getParameterStorageClasses) doesn't work with tuples as parameters

https://issues.dlang.org/show_bug.cgi?id=17495 --- Comment #2 from github-bugzi...@puremagic.com --- Commits pushed to master at https://github.com/dlang/dmd https://github.com/dlang/dmd/commit/bb9d0d02242e8b928b7f9c554d46675bc226312f fix Issue 17495 - __traits(getParameterStorageClasses)

Re: Makefile experts, unite!

On Mon, 2017-06-12 at 21:27 +0200, Jacob Carlborg via Digitalmars-d wrote: > […] > the  > makefiles, just recently [1]. And not just the makefiles, now there's > a  > Visual Studio project that needs to kept up to date as well. > > [1] https://github.com/dlang/dmd/pull/6837 There should only

[Issue 17495] __traits(getParameterStorageClasses) doesn't work with tuples as parameters

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

Re: Weird template instantiation problem

Well, I had kind of found a workaround (changing the return type to return the element and not the index) which I didn't like too much (what if there are duplicates?). Now that I've found a "proper" workaround well, I'm still interested in knowing the reason, if possible, or if it's a

Re: Makefile experts, unite!

Sebastien Alaiwan wrote: On Monday, 12 June 2017 at 06:38:34 UTC, ketmar wrote: Sebastien Alaiwan wrote: The selling points, to me, are: 1) the automatic dependency detection through filesystem hooks 2) recipes also are dependencies 3) the genericity/low-level. I believe build systems should

Re: Isn't it about time for D3?

Sebastien Alaiwan wrote: On Sunday, 11 June 2017 at 17:59:54 UTC, ketmar wrote: Guillaume Piolat wrote: On Saturday, 10 June 2017 at 23:30:18 UTC, Liam McGillivray wrote: I realize that there are people who want to continue using D as it is, but those people may continue to use D2. Well,

Re: Makefile experts, unite!

On Tuesday, June 13, 2017 05:38:37 Sebastien Alaiwan via Digitalmars-d wrote: > On Monday, 12 June 2017 at 07:00:46 UTC, Jonathan M Davis wrote: > > On Monday, June 12, 2017 06:34:31 Sebastien Alaiwan via > > > > Digitalmars-d wrote: > >> On Monday, 12 June 2017 at 06:30:16 UTC, ketmar wrote: >

atomic operations compared to c++

I'm trying to port some simple lock-free algorithm to D and as the docs are quite minimal I'm stuck a little bit. The memory order seem to be ok: MemoryOrder.acq -> C++ accquire MemoryOrder.rel -> C++ release MemoryOrder.raw -> C++ relaxed MemoryOrder.seq -> C++ seq_cst or acq_rel (the

Re: Makefile experts, unite!

On Monday, 12 June 2017 at 15:57:13 UTC, Meta wrote: On Monday, 12 June 2017 at 06:34:31 UTC, Sebastien Alaiwan wrote: On Monday, 12 June 2017 at 06:30:16 UTC, ketmar wrote: Jonathan M Davis wrote: It's certainly a pain to edit the makefiles though and don't forget those Great Copying

Re: Isn't it about time for D3?

On Sunday, 11 June 2017 at 17:59:54 UTC, ketmar wrote: Guillaume Piolat wrote: On Saturday, 10 June 2017 at 23:30:18 UTC, Liam McGillivray wrote: I realize that there are people who want to continue using D as it is, but those people may continue to use D2. Well, no thanks. The very same