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. They must have changed something in the C environment or something and I don't have a clue what's going on. I found the problem. strip in binutils 2.30 is broken.

Re: Sealed classes - would you want them in D? (v2)

On Saturday, 19 May 2018 at 04:01:18 UTC, KingJoffrey wrote: So I've come full circle again, and believe my idea is worth further consideration. how about this (use a proper annotation). This will be less likely to confuse anyone from other languages. e.g --- module test;

Re: Sealed classes - would you want them in D? (v2)

On Saturday, 19 May 2018 at 09:37:56 UTC, Uknown wrote: The point was encapsulation as you defined it was broken. private members were directly modified outside their class. In your words, everyone was a friend. This is why we have coding standards ;-)

[Issue 18874] New: Add thatneedle.com to organizations using D

https://issues.dlang.org/show_bug.cgi?id=18874 Issue ID: 18874 Summary: Add thatneedle.com to organizations using D Product: D Version: D2 Hardware: x86 OS: Mac OS X Status: NEW Severity: enhancement

[Issue 18874] Add thatneedle.com to organizations using D

https://issues.dlang.org/show_bug.cgi?id=18874 m...@thatneedle.com changed: What|Removed |Added CC||m...@thatneedle.com --

Re: DIP 1014:Hooking D's struct move semantics--Community Review Round 1

On 18/05/18 22:57, kinke wrote: I checked, and the reason is that D and C++ use a different ABI wrt. by-value passing of non-POD arguments. C++ indeed passes a reference to a caller-allocated rvalue, not just on Win64; that makes it trivial, as there are no moves across call boundaries. But

[Issue 15475] Ddoc code sample with unbalanced paren comes out as macro

https://issues.dlang.org/show_bug.cgi?id=15475 --- Comment #7 from github-bugzi...@puremagic.com --- Commits pushed to master at https://github.com/dlang/dmd https://github.com/dlang/dmd/commit/e0e23b7250401521c8db05c079ae2b59408afb0e Fix Issue 15475 - Fix more cases

[Issue 15475] Ddoc code sample with unbalanced paren comes out as macro

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

Re: Sealed classes - would you want them in D? (v2)

On Saturday, 19 May 2018 at 07:57:39 UTC, KingJoffrey wrote: On Saturday, 19 May 2018 at 04:01:18 UTC, KingJoffrey wrote: [...] module test; @safeinterface class Dog { private string noiseType = "woof"; public string makeNoise() { return this.noiseType;

Re: auto: useful, annoying or bad practice?

On Friday, 18 May 2018 at 16:25:52 UTC, Neia Neutuladh wrote: On Friday, 18 May 2018 at 10:09:20 UTC, Chris wrote: In a way Java has slowly been moving in that direction anyway, cf. this answer [2] that reminded me of D's `auto` return type. [2]

Re: Sealed classes - would you want them in D? (v2)

On Saturday, 19 May 2018 at 09:10:32 UTC, KingJoffrey wrote: On Saturday, 19 May 2018 at 08:32:28 UTC, Uknown wrote: I ported your example to Java. Surprisingly, it compiled and executed just fine: All I see, is a class, with static members. How else would it work? This is the equivalent

Found on proggit: simple treap language benchmark, includes D

D does well, comes in second on Mac/Win/linux: https://github.com/frol/completely-unscientific-benchmarks https://www.reddit.com/r/programming/comments/8jbfa7/naive_benchmark_treap_implementation_of_c_rust/

Re: Sealed classes - would you want them in D? (v2)

On Saturday, 19 May 2018 at 08:32:28 UTC, Uknown wrote: I ported your example to Java. Surprisingly, it compiled and executed just fine: All I see, is a class, with static members. How else would it work? This is the equivalent of my D example, in Java: ( it won't even compile. phew! )

Re: Sealed classes - would you want them in D? (v2)

On Saturday, 19 May 2018 at 04:01:18 UTC, KingJoffrey wrote: Mmm.. that brings me back to the idea of sealed at the class level again. class A { private int x; private(this) int y; // imagine if you have lots of private variables. // this could become pretty

[Issue 18796] std.algorithm.substitute asserts on empty range

https://issues.dlang.org/show_bug.cgi?id=18796 Andrei Vasile changed: What|Removed |Added CC|

[Issue 18876] New: Contradiction in Spec Concerning Properties

https://issues.dlang.org/show_bug.cgi?id=18876 Issue ID: 18876 Summary: Contradiction in Spec Concerning Properties Product: D Version: D2 Hardware: All OS: All Status: NEW Severity: major

[Issue 13741] std.traits.moduleName & packageName do not work with functions that have parameters

https://issues.dlang.org/show_bug.cgi?id=13741 --- Comment #1 from github-bugzi...@puremagic.com --- Commits pushed to master at https://github.com/dlang/phobos https://github.com/dlang/phobos/commit/593a4e2e39312daef00023f924a0c45af1cf082c fix issue 13741 - std.traits.moduleName does not work

Re: is ==

On Saturday, 19 May 2018 at 04:30:24 UTC, Jonathan M Davis wrote: On Saturday, May 19, 2018 03:32:53 Neia Neutuladh via Digitalmars-d-learn wrote: > Of course, the most notable case where using == with null is > a terrible idea is dynamic arrays, and that's the case where > the compiler

Re: C API / const char *text / std.string.toStringz pointer is always NULL on C side

On Saturday, 19 May 2018 at 17:33:08 UTC, Robert M. Münch wrote: On 2018-05-18 14:42:17 +, Adam D. Ruppe said: A value struct return is actually done via a hidden pointer parameter (so the function can construct it in-place for the caller, a standard optimization), so it just shifted all

Real Int24

Is there any way to create an int24 type that behaves just like any other built in type without having to reimplement everything?

[Issue 18878] New: Short-circuiting && not behaving correctly

https://issues.dlang.org/show_bug.cgi?id=18878 Issue ID: 18878 Summary: Short-circuiting && not behaving correctly Product: D Version: D2 Hardware: All OS: All Status: NEW Severity: regression

[Issue 18880] New: [REG2.079] Miscompilation of unittests when two are mixed-in on one line

https://issues.dlang.org/show_bug.cgi?id=18880 Issue ID: 18880 Summary: [REG2.079] Miscompilation of unittests when two are mixed-in on one line Product: D Version: D2 Hardware: x86 OS: Mac OS X

[Issue 18880] [REG2.079] Miscompilation of unittests when two are mixed-in on one line

https://issues.dlang.org/show_bug.cgi?id=18880 johanenge...@weka.io changed: What|Removed |Added Hardware|x86 |All OS|Mac OS X

[Issue 18877] New: std.allocator: RCIAllocator's .alignment() method is not readable at compile-time

https://issues.dlang.org/show_bug.cgi?id=18877 Issue ID: 18877 Summary: std.allocator: RCIAllocator's .alignment() method is not readable at compile-time Product: D Version: D2 Hardware: All OS: All

Re: Sealed classes - would you want them in D? (v2)

On Saturday, 19 May 2018 at 04:01:18 UTC, KingJoffrey wrote: On Friday, 18 May 2018 at 16:24:24 UTC, Gheorghe Gabriel wrote: On Friday, 18 May 2018 at 15:57:06 UTC, bachmeier wrote: On Friday, 18 May 2018 at 15:40:52 UTC, KingJo class A { private int x; private(this) int y; } I agree

Override member variables

I've worked with a lot of programming languages and I've found something interesting in Kotlin. You can override member variables. Would you like to have this feature in D? class Rectangle { int width = 0; int height = 0; } class Table : Rectangle { override int width = 10;

Re: C API / const char *text / std.string.toStringz pointer is always NULL on C side

On 2018-05-18 14:42:17 +, Adam D. Ruppe said: On Friday, 18 May 2018 at 14:06:11 UTC, Robert M. Münch wrote: So, having a wrong return-type here, resulted in the const char *text parameter always being NULL. Not sure I understand the relation but looks strange to me... at least not very

[Issue 18879] !is doesn't highlight correctly

https://issues.dlang.org/show_bug.cgi?id=18879 Manu changed: What|Removed |Added Assignee|nob...@puremagic.com|r.sagita...@gmx.de --

Re: Real Int24

On Saturday, 19 May 2018 at 18:19:35 UTC, IntegratedDimensions wrote: Is there any way to create an int24 type that behaves just like any other built in type without having to reimplement everything? In fact, what I'd like to do is create an arbitrary type: struct atype(T) { } where

[Issue 18879] New: !is doesn't highlight correctly

https://issues.dlang.org/show_bug.cgi?id=18879 Issue ID: 18879 Summary: !is doesn't highlight correctly Product: D Version: D2 Hardware: All OS: All Status: NEW Severity: normal Priority: P1

[Issue 18846] VisualD - show vtable in debugger

https://issues.dlang.org/show_bug.cgi?id=18846 Rainer Schuetze changed: What|Removed |Added CC||r.sagita...@gmx.de

[Issue 18880] [REG2.079] Miscompilation of unittests when two are mixed-in on one line

https://issues.dlang.org/show_bug.cgi?id=18880 --- Comment #1 from johanenge...@weka.io --- Related issue discussing the mixin linecount problem: https://issues.dlang.org/show_bug.cgi?id=2887 --

[Issue 18868] Separate compilation generates two static this functions, runs it twice

https://issues.dlang.org/show_bug.cgi?id=18868 --- Comment #2 from johanenge...@weka.io --- Extra testcase that must be added and considered (currently works): ``` static foreach(s; ["666", "777"]) { mixin(genCtor(s)); } int i; string genCtor(string a) { return "static this() { i += " ~

[Issue 18875] New: String literals can't disambiguate between const(char)[] and const(char)* overload.

https://issues.dlang.org/show_bug.cgi?id=18875 Issue ID: 18875 Summary: String literals can't disambiguate between const(char)[] and const(char)* overload. Product: D Version: D2 Hardware: All OS: All

[Issue 18415] Typedef ignores @disabled default constructor

https://issues.dlang.org/show_bug.cgi?id=18415 --- Comment #2 from github-bugzi...@puremagic.com --- Commits pushed to master at https://github.com/dlang/phobos https://github.com/dlang/phobos/commit/2cd3b5dac201c4168e242adfe94996fd67050f53 fix issue 18415 - Typedef ignores `@disabled` default

Re: Sealed classes - would you want them in D? (v2)

On Saturday, 19 May 2018 at 09:49:39 UTC, KingJoffrey wrote: On Saturday, 19 May 2018 at 09:37:56 UTC, Uknown wrote: The point was encapsulation as you defined it was broken. private members were directly modified outside their class. In your words, everyone was a friend. This is why we

[Issue 13741] std.traits.moduleName & packageName do not work with functions that have parameters

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

Re: Override member variables

On 05/19/2018 11:09 AM, Gheorghe Gabriel wrote: > I've worked with a lot of programming languages and I've found something > interesting in Kotlin. You can override member variables. Would you like > to have this feature in D? It's needed in C++ and I'm sure any object-oriented programming

Re: Sealed classes - would you want them in D? (v2)

On Thursday, 17 May 2018 at 10:34:18 UTC, Zoadian wrote: If class level protection is added, please do not call it sealed. People from c++ might be suprised by 'private' already. We do not have to confuse those c#ies too. I thought the same. Module level protection is enough to hide

[Issue 18846] VisualD - show vtable in debugger

https://issues.dlang.org/show_bug.cgi?id=18846 --- Comment #2 from Manu --- Right, I've noticed that our pointers don't seem to show symbol names like C++ does... why is that? Is that possible to fix? The experience should match C++. --

Re: is ==

On Saturday, 19 May 2018 at 01:31:38 UTC, Jonathan M Davis wrote: On Friday, May 18, 2018 23:53:12 IntegratedDimensions via Digitalmars-d- learn wrote: Why does D complain when using == to compare with null? Is there really any technical reason? if one just defines == null to is null then

[Issue 18879] !is doesn't highlight correctly

https://issues.dlang.org/show_bug.cgi?id=18879 --- Comment #1 from Rainer Schuetze --- `in` and `is` can be both operators or keywords depending on context, so different colors are expected. A preceding `!` is a separate token, i.e. there can be arbitrary spaces and comments

[Issue 18879] !is doesn't highlight correctly

https://issues.dlang.org/show_bug.cgi?id=18879 --- Comment #2 from Manu --- I think they should both be highlighted when used both as operators and as keywords... so I don't think that distinction of case matters? --

[Issue 18880] [REG2.079] Miscompilation of unittests when two are mixed-in on one line

https://issues.dlang.org/show_bug.cgi?id=18880 --- Comment #2 from johanenge...@weka.io --- Things are worse: ``` static foreach(s; ["666", "777"]) { mixin(genTest(s)); } int i; string genTest(string a) { return "unittest { i += " ~ a ~ "; }"; } void main() { assert(i == 0 + 666 +

Re: Error about constructor calls in loops/labels, but there are no loops and labels?

On Saturday, May 19, 2018 22:54:16 Yuxuan Shui via Digitalmars-d wrote: > On Thursday, 17 May 2018 at 20:32:23 UTC, Steven Schveighoffer > > wrote: > > On 5/17/18 4:25 PM, DarkHole wrote: > >> On Thursday, 17 May 2018 at 20:02:19 UTC, Steven Schveighoffer > >> > >> wrote: > >>> On 5/17/18 3:55 PM,

[Issue 18881] New: extern(C++) classes don't work properly in debuginfo

https://issues.dlang.org/show_bug.cgi?id=18881 Issue ID: 18881 Summary: extern(C++) classes don't work properly in debuginfo Product: D Version: D2 Hardware: x86 OS: Windows Status: NEW Severity:

[Issue 18881] extern(C++) classes don't work properly in debuginfo

https://issues.dlang.org/show_bug.cgi?id=18881 Manu changed: What|Removed |Added Assignee|nob...@puremagic.com|r.sagita...@gmx.de --

[Issue 18883] New: Revert workarounds expediting conversion of backend to D

https://issues.dlang.org/show_bug.cgi?id=18883 Issue ID: 18883 Summary: Revert workarounds expediting conversion of backend to D Product: D Version: D2 Hardware: All OS: All Status: NEW

Re: auto: useful, annoying or bad practice?

On Sunday, 20 May 2018 at 00:44:13 UTC, I love Ice Cream wrote: Which brings me to where it probably is not a good place for it...in the return fadeclaration of a function/method. I'm very close to saying, even after having read some of the comments that try justifying it, that 100% of the

[Issue 18878] Short-circuiting && not behaving correctly

https://issues.dlang.org/show_bug.cgi?id=18878 Basile B. changed: What|Removed |Added Status|NEW |RESOLVED CC|

[Issue 18115] [REG2.078-b1] case where && is not shortcut anymore in CTFE

https://issues.dlang.org/show_bug.cgi?id=18115 Basile B. changed: What|Removed |Added CC||turkey...@gmail.com ---

Re: Can I infer the type from this?

On Sunday, 20 May 2018 at 01:41:03 UTC, Dr.No wrote: I'd like to pass a symbol as paramater (class static member0 and at same time get the type of this, something like this: template myTemp(alias s) { enum myTemp = templateFunction!(??)(s.stringof); } the templateFunction has this

[Issue 14086] Invalid extern C++ name for constructor / destructor

https://issues.dlang.org/show_bug.cgi?id=14086 Manu changed: What|Removed |Added CC||turkey...@gmail.com --- Comment

Re: Error about constructor calls in loops/labels, but there are no loops and labels?

On Sunday, 20 May 2018 at 02:53:10 UTC, KingJoffrey wrote: On Sunday, 20 May 2018 at 00:05:39 UTC, Jonathan M Davis wrote: As I understand it, in general, Walter is against doing ... All I ever hear, is walter walter walter While it's mildly refreshing that you found something new to

Re: Error about constructor calls in loops/labels, but there are no loops and labels?

On Thursday, 17 May 2018 at 20:32:23 UTC, Steven Schveighoffer wrote: On 5/17/18 4:25 PM, DarkHole wrote: On Thursday, 17 May 2018 at 20:02:19 UTC, Steven Schveighoffer wrote: On 5/17/18 3:55 PM, DarkHole wrote: This strange code - https://run.dlang.io/is/BKgv49 - fails with error "Error:

C style callbacks fix for member callbacks

I have a member callback that I want to use as a C callback. This is impossible due to the `hidden this` passed as the "first" parameter. The callback already makes it's last value a user pointer which I use as a "this". If I make my method static extern(C) then there is no crash and

Re: is ==

On Saturday, May 19, 2018 17:13:36 Neia Neutuladh via Digitalmars-d-learn wrote: > I don't think I've ever wanted to distinguish a zero-length slice > of an array from a null array. It's safer if you don't, because it's so easy to end up with a dynamic array that is empty instead of null, and

Re: is ==

On Sunday, 20 May 2018 at 00:19:28 UTC, Jonathan M Davis wrote: On Saturday, May 19, 2018 17:50:50 IntegratedDimensions via Digitalmars-d- learn wrote: So, ultimately what I feels like is that you are actually arguing for == null to be interpreted as is null but you don't realize it yet. Not

Re: Sealed classes - would you want them in D? (v2)

On Saturday, 19 May 2018 at 17:15:45 UTC, Neia Neutuladh wrote: On Saturday, 19 May 2018 at 09:49:39 UTC, KingJoffrey wrote: On Saturday, 19 May 2018 at 09:37:56 UTC, Uknown wrote: The point was encapsulation as you defined it was broken. private members were directly modified outside their

Re: Error about constructor calls in loops/labels, but there are no loops and labels?

On Sunday, 20 May 2018 at 00:05:39 UTC, Jonathan M Davis wrote: As I understand it, in general, Walter is against doing ... All I ever hear, is walter walter walter mmm..takes me back to my childhood.. https://www.youtube.com/watch?v=-yZHveWFvqM

Re: is ==

On Sunday, 20 May 2018 at 02:09:47 UTC, Jonathan M Davis wrote: On Sunday, May 20, 2018 01:51:50 IntegratedDimensions via Digitalmars-d- learn wrote: Simply require == null as is null and be done with it. That would be flat out wrong for dynamic arrays, because then auto result = arr == null

Re: Can I infer the type from this?

On Sunday, 20 May 2018 at 02:01:20 UTC, Alex wrote: On Sunday, 20 May 2018 at 01:41:03 UTC, Dr.No wrote: I'd like to pass a symbol as paramater (class static member0 and at same time get the type of this, something like this: template myTemp(alias s) { enum myTemp =

Re: is ==

On Saturday, May 19, 2018 17:50:50 IntegratedDimensions via Digitalmars-d- learn wrote: > So, ultimately what I feels like is that you are actually arguing > for == null to be interpreted as is null but you don't realize it > yet. Not really, no. Having foo == null be rewritten to foo is null

Re: auto: useful, annoying or bad practice?

'auto' in the sense that C# and other languages use 'var' makes perfect sense. There is nothing wrong with it and it takes out redundant 'noise': var i = "This is a string"; // don't need to know two times that this is a string. var j = SomethingThatReturns(); // IDE or function docs

Re: Sealed classes - would you want them in D? (v2)

On Saturday, 19 May 2018 at 21:25:37 UTC, 0xEAB wrote: On Thursday, 17 May 2018 at 10:34:18 UTC, Zoadian wrote: If class level protection is added, please do not call it sealed. People from c++ might be suprised by 'private' already. We do not have to confuse those c#ies too. I thought the

[Issue 18881] extern(C++) classes don't work properly in debuginfo

https://issues.dlang.org/show_bug.cgi?id=18881 --- Comment #1 from Manu --- Sadly, more of my D code is extern(C++) than not >_< --

Re: How is == operator implemented for string type?

On Wednesday, 16 May 2018 at 18:56:26 UTC, Steven Schveighoffer wrote: On 5/16/18 2:45 PM, Dr.No wrote: where is the actual source code implementation? https://github.com/dlang/druntime/blob/7e3b4086fee8f2e2a6882942c677acc28df527ee/src/object.d#L3479 -Steve thanks

Re: Sealed classes - would you want them in D? (v2)

On Saturday, 19 May 2018 at 17:38:48 UTC, Gheorghe Gabriel wrote: If you have sealed class A { private { // members } } Then you can't use the defualt 'private' if you need it for a specific member. But if sealed is an access type of a member, 99% you will use sealed insted

Re: Override member variables

On Saturday, 19 May 2018 at 18:09:56 UTC, Gheorghe Gabriel wrote: And of course, you cannot override private members. wtf! what do you mean we cannot override private members! that's at the core of D! what's with you anyway! (ohh. to those new to the forums, that's friendly sarcasm, cause

Re: Error about constructor calls in loops/labels, but there are no loops and labels?

On Sunday, 20 May 2018 at 03:13:12 UTC, Neia Neutuladh wrote: While it's mildly refreshing that you found something new to talk about, it would be nice if you found something productive to say. You're merely complaining that a person who has spent about two decades on D (for free), who has

Re: is ==

Furthermore: https://issues.dlang.org/show_bug.cgi?id=3889 Shows real problems. You argue from the side that the bug already exists so we must work around it because we can't go back and "fix things". Who says? D has had breaking changes in the past so it is not a deal breaker. It is also a

[Issue 18846] VisualD - show vtable in debugger

https://issues.dlang.org/show_bug.cgi?id=18846 --- Comment #3 from Manu --- I just installed that build. I can see an item in place of the vtable: -tclass 0x02D2 Source.Base +[Source.Derived]0x02D2 Source.Derived object.Object

Can I infer the type from this?

I'd like to pass a symbol as paramater (class static member0 and at same time get the type of this, something like this: template myTemp(alias s) { enum myTemp = templateFunction!(??)(s.stringof); } the templateFunction has this signature: int templateFunction(T)(string

[Issue 18882] __gshared not displaying in debuginfo

https://issues.dlang.org/show_bug.cgi?id=18882 --- Comment #1 from Manu --- Perhaps it's the extern(C++) that's the problem? That would explain why I have debug problems a lot. --

[Issue 18882] __gshared not displaying in debuginfo

https://issues.dlang.org/show_bug.cgi?id=18882 Manu changed: What|Removed |Added Assignee|nob...@puremagic.com|r.sagita...@gmx.de --

[Issue 18882] New: __gshared not displaying in debuginfo

https://issues.dlang.org/show_bug.cgi?id=18882 Issue ID: 18882 Summary: __gshared not displaying in debuginfo Product: D Version: D2 Hardware: x86_64 OS: Windows Status: NEW Severity: normal

Re: is ==

On Sunday, May 20, 2018 01:51:50 IntegratedDimensions via Digitalmars-d- learn wrote: > Simply require == null as is null and be done with it. That would be flat out wrong for dynamic arrays, because then auto result = arr == null and int[] nullArr; auto result = arr == nullArr; would have