Constructor - the both look the same

Why does it come up with this? source/setup.d(40,16): Error: constructor inputjex.InputJex.this (Vector2!float pos, int fontSize, InputType type = cast(InputType)0) is not callable using argument types (Vector2!float, int, InputType) dmd failed with exit code 1.

[Issue 15785] [DMD HEAD] Spurious warning when calling protected super

https://issues.dlang.org/show_bug.cgi?id=15785 Martin Nowak changed: What|Removed |Added CC||c...@dawg.eu --- Comment #1

Re: BZ2 library

On Saturday, 12 March 2016 at 06:07:25 UTC, Mike Parker wrote: [...] I used visual studio 2013 to build the libraries With dflag -m64 and dub flag --arch=x86_64, this happens Running: dub build --arch=x86_64 ## Warning for package rsdlib ## The following compiler flags have

Re: BZ2 library

On Saturday, 12 March 2016 at 05:16:37 UTC, stunaep wrote: I'm really having a hard time using bzp (and later I need gzip and lzma). So I added this bzip2 D interface to my DUB dependencies "dependencies" : { "bzip2": "~>0.1.0" } I downloaded the bzip2 source code and compiled

Re: BZ2 library

On Saturday, 12 March 2016 at 05:16:37 UTC, stunaep wrote: I'm really having a hard time using bzp (and later I need gzip and lzma). So I added this bzip2 D interface to my DUB dependencies "dependencies" : { "bzip2": "~>0.1.0" } I downloaded the bzip2 source code and compiled

BZ2 library

I'm really having a hard time using bzp (and later I need gzip and lzma). So I added this bzip2 D interface to my DUB dependencies "dependencies" : { "bzip2": "~>0.1.0" } I downloaded the bzip2 source code and compiled it for windows 32bit (will 64 bit work with dmd2?). Then I

Re: Simple call to static member function

On Friday, 11 March 2016 at 23:14:48 UTC, ag0aep6g wrote: On 11.03.2016 23:47, WhatMeWorry wrote: [...] This suggests that you simply `import ResourceManager;` in main.d. [...] Very good. Thanks for the fix and the pointers. I'm porting C++ code over, and it has corrupted me. I'll

[Issue 15790] New: The GC frees managed members made w/ allocator.make, causing memory corruption

https://issues.dlang.org/show_bug.cgi?id=15790 Issue ID: 15790 Summary: The GC frees managed members made w/ allocator.make, causing memory corruption Product: D Version: D2 Hardware: All OS: All

Re: Potential GSoC project - GC improvements

On 12/03/16 4:13 AM, Jeremy DeHaan wrote: Thank you all for the feedback. I think I might still need a little more feedback as to what the project should actually entail, but here's what it's looking like so far: Implement lock free allocation using std.experimental.allocator's freelists

[Issue 4852] core.demangle cannot demangle functions with class/struct return types

https://issues.dlang.org/show_bug.cgi?id=4852 Andrew Trotman changed: What|Removed |Added Status|ASSIGNED|RESOLVED

Re: dmd-built dmd is faster that ldc-built dmd or gdc-built dmd?

On Friday, 11 March 2016 at 15:09:26 UTC, Iain Buclaw wrote: Yes, I know. And if I were to say which behaviour is desired. I'd say GDC is doing the right thing. Marking all functions as 'weak' is a terrible idea on both DMD's and LDC's part. I distinctly remember Daniel and me having to

Re: Simple call to static member function

On 11.03.2016 23:47, WhatMeWorry wrote: --- main.d void main(string[] argv) { ResourceManager.LoadShader("VertexShader.glsl", "FragmentShader.glsl", "filler", "sprite"); --- File ResourceManager.d

Re: Simple call to static member function

On Friday, 11 March 2016 at 22:47:00 UTC, WhatMeWorry wrote: main.d(173): Error: undefined identifier 'LoadShader' in module 'ResourceManager' Please show enough of the code that I can actually try to compile it myself. In particular, I need to see how you handled the imports since that is

Simple call to static member function

--- main.d void main(string[] argv) { ResourceManager.LoadShader("VertexShader.glsl", "FragmentShader.glsl", "filler", "sprite"); --- File ResourceManager.d class ResourceManager {

Re: My whereabouts

On Friday, 11 March 2016 at 22:27:54 UTC, Nordlöw wrote: On Friday, 11 March 2016 at 09:39:34 UTC, Jonathan M Davis wrote: The Big O stuff that he worked on was done as part of working on the new containers, but it's separate from them. It provides a way to mark functions with their complexity

Re: My whereabouts

On Friday, 11 March 2016 at 09:39:34 UTC, Jonathan M Davis wrote: The Big O stuff that he worked on was done as part of working on the new containers, but it's separate from them. It provides a way to mark functions with their complexity and do inference and the like with it. - Jonathan M

[Issue 15714] [ndslice] byElement seems to be missing some slicing primitives

https://issues.dlang.org/show_bug.cgi?id=15714 --- Comment #1 from github-bugzi...@puremagic.com --- Commits pushed to master at https://github.com/D-Programming-Language/phobos https://github.com/D-Programming-Language/phobos/commit/df4a363e61fd06d6338f2724e89c73e9d56cf1d1 fix issue 15714

[Issue 15714] [ndslice] byElement seems to be missing some slicing primitives

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

[Issue 15715] [ndslice] rangeHasMutableElements is not defined

https://issues.dlang.org/show_bug.cgi?id=15715 --- Comment #1 from github-bugzi...@puremagic.com --- Commits pushed to master at https://github.com/D-Programming-Language/phobos https://github.com/D-Programming-Language/phobos/commit/9b8a297690a3215f45eda60991c01d39c76f4389 fix issue 15715

[Issue 15789] ICE Assert in TemplateInstance semanticTiargs

https://issues.dlang.org/show_bug.cgi?id=15789 ag0ae...@gmail.com changed: What|Removed |Added Keywords||ice CC|

[Issue 15788] ICE assert triggered on overloaded function

https://issues.dlang.org/show_bug.cgi?id=15788 ag0ae...@gmail.com changed: What|Removed |Added Keywords||ice CC|

[Issue 15784] Overload set constructor call should be supported from inside a constructor

https://issues.dlang.org/show_bug.cgi?id=15784 Martin Nowak changed: What|Removed |Added CC||c...@dawg.eu --- Comment #1

[Issue 15784] Overload set constructor call should be supported from inside a constructor

https://issues.dlang.org/show_bug.cgi?id=15784 Issue 15784 depends on issue 15744, which changed state. Issue 15744 Summary: [REG2.067] (SIGABRT) Error: overloadset t.Bar.__ctor is aliased to a function https://issues.dlang.org/show_bug.cgi?id=15744 What|Removed

[Issue 15744] [REG2.067] (SIGABRT) Error: overloadset t.Bar.__ctor is aliased to a function

https://issues.dlang.org/show_bug.cgi?id=15744 --- Comment #6 from github-bugzi...@puremagic.com --- Commits pushed to stable at https://github.com/D-Programming-Language/dmd https://github.com/D-Programming-Language/dmd/commit/1b4eefa55a3933ee214576612d1cbc81b5426d04 fix Issue 15744 - (SIGABRT)

GSoC

I am interested in working with you this summer as a GSoC student. I have good knowledge of Python, Javascript and C++ (related to the mentioned pre-requisites) as well as in HTML, CSS and SQL. I feel that I fulfill the pre-requisites for working with you. I am also a part of Programming and

[Issue 15789] New: ICE Assert in TemplateInstance semanticTiargs

https://issues.dlang.org/show_bug.cgi?id=15789 Issue ID: 15789 Summary: ICE Assert in TemplateInstance semanticTiargs Product: D Version: D2 Hardware: All OS: All Status: NEW Severity: normal

[Issue 14447] adding isRandomAccessRange!S causes std.array unittests to fail to compile

https://issues.dlang.org/show_bug.cgi?id=14447 thomas.bock...@gmail.com changed: What|Removed |Added CC||thomas.bock...@gmail.com ---

code-d 0.10.1 released (D support for vscode)

I just released a new version of code-d, it now supports projects without any dub.json file which some people probably will like. This is really useful for standalone projects with a custom build system like writing an OS/Kernel or other projects that don't want to use dub. Additionally some

Re: asserting dmd has a problem?

On Fri, 2016-03-11 at 18:47 +, Adam D. Ruppe via Digitalmars-d- learn wrote: > On Friday, 11 March 2016 at 18:45:12 UTC, Russel Winder wrote: > > > > The following code compiles fine using DMD 2.70.2: > Using -release? Hummm… surreptitious -release I had missed. That deals with that. Many

Re: Iterating over thread local storage variables

On Friday, 11 March 2016 at 18:45:13 UTC, Anonymouse wrote: On Friday, 11 March 2016 at 17:33:43 UTC, sigod wrote: On Friday, 11 March 2016 at 17:03:38 UTC, Anonymouse wrote: On Friday, 11 March 2016 at 15:21:38 UTC, maik klein wrote: [...] As a drive-by comment, mind that

Re: asserting dmd has a problem?

On Friday, 11 March 2016 at 18:45:12 UTC, Russel Winder wrote: The following code compiles fine using DMD 2.70.2: Using -release? Or catching the AssertError?

Re: Iterating over thread local storage variables

On Friday, 11 March 2016 at 17:33:43 UTC, sigod wrote: On Friday, 11 March 2016 at 17:03:38 UTC, Anonymouse wrote: On Friday, 11 March 2016 at 15:21:38 UTC, maik klein wrote: static Singleton!T get() { if (!instantiated_) {

asserting dmd has a problem?

Clearly I am missing something very, very simple, but… The following code compiles fine using DMD 2.70.2: writeln(play_bin); assert(play_bin is null); assert(play_bin !is null); with the output: null on executing the code. I have two comments:

Re: Use of GUID constants

Oh, it was https://github.com/D-Programming-Language/druntime/pull/1472

Re: GC scan for pointers

On Thursday, 10 March 2016 at 10:58:41 UTC, thedeemon wrote: On Wednesday, 9 March 2016 at 15:14:02 UTC, Gerald Jansen wrote: enum n = 100_000_000; // some big number auto a = new ulong[](n); auto b = new char[8][](n); struct S { ulong x; char[8] y; } auto c = new S[](n); will the

Re: Use of GUID constants

On Wednesday, 9 March 2016 at 18:35:31 UTC, KlausO wrote: So maybe they should be declared as "extern GUID ..." because they also seem to be defined in windows\lib\uuid.lib which comes with DMD. Declarations come from mingw and mingw doesn't have uuid.lib:

[Issue 15788] New: ICE assert triggered on overloaded function

https://issues.dlang.org/show_bug.cgi?id=15788 Issue ID: 15788 Summary: ICE assert triggered on overloaded function Product: D Version: D2 Hardware: All OS: All Status: NEW Severity: regression

Re: std.allocator issues

Am Tue, 8 Mar 2016 16:35:45 -0500 schrieb Andrei Alexandrescu : > On 3/7/16 11:53 PM, Marco Leise wrote: > > By the way: jemalloc has `mallocx()` to allocate at least N > > bytes and `sallocx()` to ask for the actual size of an > > allocation. > > I know. Jason

[Issue 15698] Compiler crash with unusual function call expression

https://issues.dlang.org/show_bug.cgi?id=15698 Johan Engelen changed: What|Removed |Added CC||jbc.enge...@gmail.com

Re: static if else behavior and is type comparison

On Fri, 11 Mar 2016 00:21:33 -0800, Ali Çehreli wrote: > You've been bitten by a common usability issue. :) > > On 03/11/2016 12:02 AM, Fynn Schröder wrote: > > static if (is(U == ubyte)) { > > pragma(msg, "is ubyte"); > > return fnUbyte(); > > } else if (is(U ==

Re: Iterating over thread local storage variables

On Friday, 11 March 2016 at 17:03:38 UTC, Anonymouse wrote: On Friday, 11 March 2016 at 15:21:38 UTC, maik klein wrote: static Singleton!T get() { if (!instantiated_) { synchronized(Singleton!T.classinfo){ if (!instance_){

Re: Iterating over thread local storage variables

On Friday, 11 March 2016 at 15:21:38 UTC, maik klein wrote: static Singleton!T get() { if (!instantiated_) { synchronized(Singleton!T.classinfo){ if (!instance_){ instance_ = new Singleton!T(); }

Re: Named arguments via struct initialization in functions

On Fri, 11 Mar 2016 14:29:39 +, Marc Schütz wrote: >> 0 "Inside tuple literal, ; never appears." >> {{;}} // a tuple not matching your specification >> {{if(foo()){}}} // a non-tuple matching your specification > > This is not a serious problem, because it just means that the

Re: Named arguments via struct initialization in functions

On Friday, 11 March 2016 at 13:26:49 UTC, Meta wrote: On Thursday, 10 March 2016 at 19:36:05 UTC, ZombineDev wrote: On Monday, 7 March 2016 at 18:21:24 UTC, Meta wrote: [...] Can you find the exact case? I'm really interested in getting proper tuple syntax support and I think that's

Re: Deduction regression or improvement?

On Friday, 11 March 2016 at 13:28:22 UTC, Hara Kenji wrote: On Wednesday, 9 March 2016 at 01:27:41 UTC, Dicebot wrote: The both cases are disabled in the bugfix PR: https://github.com/D-Programming-Language/dmd/pull/4818 I think that T should be deduced to the typeof(true ? cs : ms) at line

[Issue 15787] core.stdc.config should be documented

https://issues.dlang.org/show_bug.cgi?id=15787 --- Comment #2 from Steven Schveighoffer --- FYI: https://github.com/D-Programming-Language/dlang.org/pull/1248 Note that core.stdc.config is specifically excluded from the menu in the same way core.stdc was, so you'll have to

[Issue 15787] core.stdc.config should be documented

https://issues.dlang.org/show_bug.cgi?id=15787 Steven Schveighoffer changed: What|Removed |Added CC|

[Issue 15786] Line buffering not activated for stdout when running D programs under Eclipse

https://issues.dlang.org/show_bug.cgi?id=15786 b2.t...@gmx.com changed: What|Removed |Added CC||b2.t...@gmx.com --- Comment #2 from

Iterating over thread local storage variables

I want to create a logger in a multithreaded system. I wanted to expose a global variable like logger.log("something"); I also wanted to reuse D's thread local global variables because that would make it easy to log in a multithreaded system. This is really easy to do, but the problem is

Re: Deduction regression or improvement?

On Friday, 11 March 2016 at 13:28:22 UTC, Hara Kenji wrote: I think that T should be deduced to the typeof(true ? cs : ms) at line [a] and typeof(true ? ms : cs) at line [b], then the two lines will get consistent deduction result T == const(S). I also thought it should deduce T == const(S),

Re: dmd-built dmd is faster that ldc-built dmd or gdc-built dmd?

On Friday, 11 March 2016 at 15:09:26 UTC, Iain Buclaw wrote: Marking all functions as 'weak' is a terrible idea on both DMD's and LDC's part. I can't judge what is best here, but LDC does not always mark functions as weak. After the DDMD switch, we have multiple def. problems on Windows

Re: Potential GSoC project - GC improvements

Thank you all for the feedback. I think I might still need a little more feedback as to what the project should actually entail, but here's what it's looking like so far: Implement lock free allocation using std.experimental.allocator's freelists (SharedFreeList? It was the only thing in

Re: dmd-built dmd is faster that ldc-built dmd or gdc-built dmd?

On Friday, 11 March 2016 at 14:46:59 UTC, Vladimir Panteleev wrote: On Friday, 11 March 2016 at 14:32:26 UTC, Iain Buclaw wrote: https://github.com/D-Programming-Language/dmd/blob/master/src/root/rmem.d#L166-L193 How memory is allocated makes a huge difference. Thanks :) After changing that

Re: dmd-built dmd is faster that ldc-built dmd or gdc-built dmd?

On Friday, 11 March 2016 at 15:04:44 UTC, Edwin van Leeuwen wrote: On Friday, 11 March 2016 at 14:46:59 UTC, Vladimir Panteleev wrote: Thanks :) After changing that to version(all), LDC is faster now. Doesn't build with GDC though (multiple definitions)... How much faster is LDC? About 10%,

Re: dmd-built dmd is faster that ldc-built dmd or gdc-built dmd?

On Friday, 11 March 2016 at 14:46:59 UTC, Vladimir Panteleev wrote: Thanks :) After changing that to version(all), LDC is faster now. Doesn't build with GDC though (multiple definitions)... How much faster is LDC?

Re: dmd-built dmd is faster that ldc-built dmd or gdc-built dmd?

On Friday, 11 March 2016 at 14:32:26 UTC, Iain Buclaw wrote: On Friday, 11 March 2016 at 13:39:04 UTC, Vladimir Panteleev wrote: Hi, In the process of setting up a new development environment, I noticed that DMD's codegen seems to outperform GDC's or LDC's when building DMD itself. I wrote

Re: dmd-built dmd is faster that ldc-built dmd or gdc-built dmd?

On Friday, 11 March 2016 at 13:39:04 UTC, Vladimir Panteleev wrote: Hi, In the process of setting up a new development environment, I noticed that DMD's codegen seems to outperform GDC's or LDC's when building DMD itself. I wrote a test script to measure the time it takes for DMD (built

Re: unit-threaded v0.6.5 - Type-parametrized tests

On Friday, 11 March 2016 at 14:26:34 UTC, Atila Neves wrote: Didn't Robert have a QuickCheck-alike as well? Yes, https://github.com/D-Programming-Language/phobos/pull/2995

Re: Named arguments via struct initialization in functions

On Friday, 11 March 2016 at 13:26:49 UTC, Meta wrote: On Thursday, 10 March 2016 at 19:36:05 UTC, ZombineDev wrote: On Monday, 7 March 2016 at 18:21:24 UTC, Meta wrote: Unfortunately this will not work. There was a tuple proposal sometime back in 2012 or 2013. I can't remember the exact

Re: unit-threaded v0.6.5 - Type-parametrized tests

On Friday, 11 March 2016 at 08:06:19 UTC, Jacob Carlborg wrote: On 2016-03-10 12:05, Atila Neves wrote: No, sorry. I haven't needed it yet. Something like this? Yes. @Types!(int, string) void testArray(T)() { import std.container; auto arr = Array!T();

[Issue 15787] New: core.stdc.config should be documented

https://issues.dlang.org/show_bug.cgi?id=15787 Issue ID: 15787 Summary: core.stdc.config should be documented Product: D Version: D2 Hardware: All OS: All Status: NEW Severity: major Priority: P1

Re: static if else behavior and is type comparison

On Friday, 11 March 2016 at 12:10:53 UTC, Artur Skawina wrote: On 03/11/16 09:21, Ali Çehreli via Digitalmars-d-learn wrote: You've been bitten by a common usability issue. :) On 03/11/2016 12:02 AM, Fynn Schröder wrote: static if (is(U == ubyte)) { } else if (is(U == ushort)) {

dmd-built dmd is faster that ldc-built dmd or gdc-built dmd?

Hi, In the process of setting up a new development environment, I noticed that DMD's codegen seems to outperform GDC's or LDC's when building DMD itself. I wrote a test script to measure the time it takes for DMD (built with different compilers) to build Phobos:

Re: Deduction regression or improvement?

On Wednesday, 9 March 2016 at 01:27:41 UTC, Dicebot wrote: Looks like regression to me. If SomeStruct contains indirections, it should be able to deduce T as const(SomeStruct). It SomeStruct is strict value type, deducing T as both SomeStruct and const(SomeStruct) would be fine. But the

Re: Named arguments via struct initialization in functions

On Thursday, 10 March 2016 at 19:36:05 UTC, ZombineDev wrote: On Monday, 7 March 2016 at 18:21:24 UTC, Meta wrote: On Monday, 7 March 2016 at 10:40:15 UTC, ZombineDev wrote: Which I don't think will cause ambiguity with delegates: auto tuple3 = { getInt() }; tuple auto tuple3 = { getInt(); };

[Issue 15781] Template type deduction failure with same-type variables with different constness

https://issues.dlang.org/show_bug.cgi?id=15781 --- Comment #1 from Kenji Hara --- Introduced in: https://github.com/D-Programming-Language/dmd/pull/4818 --

[Issue 15782] [Reg 2.071-devel] something about the const/non-const types in TypeTuples changed

https://issues.dlang.org/show_bug.cgi?id=15782 --- Comment #3 from John Colvin --- https://issues.dlang.org/show_bug.cgi?id=11577 --

[Issue 15786] Line buffering not activated for stdout when running D programs under Eclipse

https://issues.dlang.org/show_bug.cgi?id=15786 --- Comment #1 from Bruno Medeiros --- *** Issue 13778 has been marked as a duplicate of this issue. *** --

[Issue 13778] Flush stream when std.stdio.writeln() is called

https://issues.dlang.org/show_bug.cgi?id=13778 Bruno Medeiros changed: What|Removed |Added Status|NEW

[Issue 15786] Line buffering not activated for stdout when running D programs under Eclipse

https://issues.dlang.org/show_bug.cgi?id=15786 Bruno Medeiros changed: What|Removed |Added CC|

[Issue 15786] New: Line buffering not activated for stdout when running D programs under Eclipse

https://issues.dlang.org/show_bug.cgi?id=15786 Issue ID: 15786 Summary: Line buffering not activated for stdout when running D programs under Eclipse Product: D Version: D2 Hardware: x86_64 OS: Windows

[Issue 15782] [Reg 2.071-devel] something about the const/non-const types in TypeTuples changed

https://issues.dlang.org/show_bug.cgi?id=15782 John Colvin changed: What|Removed |Added CC|

Re: New Article: My Experience Porting Python Dateutil's Date Parser to D

On Thursday, 10 March 2016 at 21:25:16 UTC, Jack Stouffer wrote: On Wednesday, 9 March 2016 at 22:12:42 UTC, Walter Bright wrote: I haven't read the article yet, but you'll get more interest by putting a summary as the first comment on reddit. Thanks for the advice, I think it caused more

Re: static if else behavior and is type comparison

On 03/11/16 09:21, Ali Çehreli via Digitalmars-d-learn wrote: > You've been bitten by a common usability issue. :) > > On 03/11/2016 12:02 AM, Fynn Schröder wrote: >> static if (is(U == ubyte)) { >> } else if (is(U == ushort)) { > > You mean 'else static if'. (Not your fault: I (and

[Issue 15782] [Reg 2.071-devel] something about the const/non-const types in TypeTuples changed

https://issues.dlang.org/show_bug.cgi?id=15782 Kenji Hara changed: What|Removed |Added Component|dmd |phobos --- Comment #1

Re: Suggested Change to Contract Syntax

On Friday, 11 March 2016 at 10:22:06 UTC, Jacob Carlborg wrote: Another advantage of the contracts would be if the caller would be responsible for running the contracts. That is currently not the case. Then a library could be shipped with contracts and it's up to the user of the library to

Re: Suggested Change to Contract Syntax

On 2016-03-10 23:57, Jonathan M Davis wrote: IMHO, at this point, inheritance is the only reason they're worth having in the language. Without inheritance, in contracts could just as easily be assertions at the top of the function, and while out contracts are certainly easier as they are now

Re: My whereabouts

On Friday, 11 March 2016 at 08:25:12 UTC, Nordlöw wrote: On Thursday, 10 March 2016 at 15:25:54 UTC, Andrei Alexandrescu wrote: What ever happened to that Big O library you were writing? Does this mean the container-library? If so what does the "Big O" stand for?

Re: static if else behavior and is type comparison

On Friday, 11 March 2016 at 08:21:33 UTC, Ali Çehreli wrote: You mean 'else static if'. (Not your fault: I (and others) wish the compiler warned about this problem.) Thanks! Such an easy mistake.. You're right Ali, it would be nice if the compiler gave a warning :)

Re: Named arguments via struct initialization in functions

On Friday, 11 March 2016 at 05:09:44 UTC, Chris Wright wrote: On Thu, 10 Mar 2016 19:01:53 +, ZombineDev wrote: On Monday, 7 March 2016 at 19:06:54 UTC, Chris Wright wrote: On Mon, 07 Mar 2016 11:06:13 +, ZombineDev wrote: The compiler should detect that this call is ambiguous and

Re: My whereabouts

On Thursday, 10 March 2016 at 15:25:54 UTC, Andrei Alexandrescu wrote: What ever happened to that Big O library you were writing? Does this mean the container-library? If so what does the "Big O" stand for? It's done and with a nice accompanying article too, I just need to allocate the

Re: static if else behavior and is type comparison

On Friday, 11 March 2016 at 08:02:41 UTC, Fynn Schröder wrote: Am I doing anything wrong here or is this a bug? You should write: static if { ... } else static if { ... } else static if { ... }

Re: static if else behavior and is type comparison

You've been bitten by a common usability issue. :) On 03/11/2016 12:02 AM, Fynn Schröder wrote: > static if (is(U == ubyte)) { > pragma(msg, "is ubyte"); > return fnUbyte(); > } else if (is(U == ushort)) { You mean 'else static if'. (Not your fault: I (and others)

Re: Hotfix release vibe.d 0.7.28

Am 10.03.2016 um 20:40 schrieb Eugene Wissner: Sönke, is your current work on core available somewhere? Since my vibe.d related work isn't stable it wouldn't a problem to use unstable core-component. It is better than rewriting later if a lot of things change. It's still in a very early state

[Issue 314] [module] Static, renamed, and selective imports are always public

https://issues.dlang.org/show_bug.cgi?id=314 Denis Shelomovskij changed: What|Removed |Added CC|

Re: unit-threaded v0.6.5 - Type-parametrized tests

On 2016-03-10 12:05, Atila Neves wrote: No, sorry. I haven't needed it yet. Something like this? Yes. @Types!(int, string) void testArray(T)() { import std.container; auto arr = Array!T(); arr.empty.shouldBeTrue; arr.insertBack(T.init); arr.empty.shouldBeFalse;

static if else behavior and is type comparison

Hi all, I'm currently working on a small utility to control the EC (embedded controller) of my notebook. I need to call an external C library and choose different methods based on the desired return type. I came up with a solution based on type checking and static if - however I ran into a