Re: Different function attributes between debug and release build

On Saturday, 9 July 2016 at 01:05:54 UTC, Walter Bright wrote: Not a bug until it is posted to Bugzilla! so if i won't post a dmd segfault there, i may assume that dmd segfault is intended behavior? then let's document it! ;-)

Re: Variadic Tuple of Structs with Mixed Types

On 07/09/2016 12:33 AM, jmh530 wrote: I'm trying to create a tuple of variadic length containing structs with mixed types. So for instance, given struct Foo(T, U) { T x; U y; } I want to create something like Tuple!(Foo!(type1, type2), Foo!(type1, type3), ..., Foo!(type1, typeN)) x;

Re: D Wiki admin - there's a few spammer to ban

On Saturday, 9 July 2016 at 02:32:20 UTC, Basile B. wrote: so far nothing appears in the usual pages and links but who know this could happend. Thanks, I cleaned it up and increased the CAPTCHA difficulty. In the future, please do not tamper with spam pages in any way, I had to intentionally

Re: Vision for the D language - stabilizing complexity?

On Friday, 8 July 2016 at 21:23:24 UTC, Timon Gehr wrote: On 08.07.2016 04:25, Andrew Godfrey wrote: Another example is "return" used for monads in eg Haskell - even if it only has one meaning in Haskell, it is too mixed up with a different meaning in other common languages. D's "static if"

Re: Vision for the D language - stabilizing complexity?

On Friday, 8 July 2016 at 18:16:03 UTC, Andrei Alexandrescu wrote: On 07/07/2016 10:25 PM, Andrew Godfrey wrote: D's "static if" - which is a killer feature if I ignore the keyword - gives me a similar feeling (though it's much less egregious than "return" in monads). "static" is a terribly

Re: Vision document for H2 2016

On 09/07/2016 5:08 AM, Andrei Alexandrescu wrote: On 07/08/2016 12:00 AM, rikki cattermole wrote: On 08/07/2016 7:55 AM, Andrei Alexandrescu wrote: https://wiki.dlang.org/Vision/2016H2 -- Andrei We really need opRef* implemented in dmd. What is that? -- Andrei As in your solution to ref

D Wiki admin - there's a few spammer to ban

see https://wiki.dlang.org/Special:RecentChanges e.g https://wiki.dlang.org/G.m.a.i.l_tecH_suPPort_Numbner!!((1_..888..269..0130_))_Gmail_Enterprise_Customer_help_desk_support_Phone_Number so far nothing appears in the usual pages and links but who know this could happend.

Re: Vision document for H2 2016

On 7/8/16 6:36 PM, Carl Vogel wrote: On Thursday, 7 July 2016 at 19:56:29 UTC, Andrei Alexandrescu wrote: On 07/07/2016 03:55 PM, Andrei Alexandrescu wrote: https://wiki.dlang.org/Vision/2016H2 -- Andrei Please provide feedback. We'll make a couple more passes before this is complete.

Re: BulletD needs your help!

On Friday, 8 July 2016 at 07:59:42 UTC, Dechcaudron wrote: Hey there, I'm sad this post hasn't called anyone's attention so far. While I am defintely interested to have BulletD become a thing, I sadly can't collaborate with it so far. It's been on my mind to give Bullet as a physics engine a

Re: Different function attributes between debug and release build

On 7/8/2016 1:04 PM, Jerry wrote: On Thursday, 7 July 2016 at 19:39:12 UTC, Lodovico Giaretta wrote: Currently, std.string.assumeUTF is inferred @nogc in release mode, while in debug mode it isn't. Should this be allowed? It can cause some problems, e.g. I have some @nogc unittests that I use

[Issue 16255] New: std.algorithm.iteration.each on opApply doesn't support ref

https://issues.dlang.org/show_bug.cgi?id=16255 Issue ID: 16255 Summary: std.algorithm.iteration.each on opApply doesn't support ref Product: D Version: D2 Hardware: All OS: All Status: NEW

Re: Vision for the D language - stabilizing complexity?

On 7/8/2016 2:33 PM, Timon Gehr wrote: On 08.07.2016 21:26, Andrei Alexandrescu wrote: Where is the reference to Walter's promotion of UB in @safe code? Only found this, but IIRC, there was another discussion:

Re: Vision for the D language - stabilizing complexity?

On 7/8/2016 2:58 PM, Ola Fosheim Grøstad wrote: On Friday, 8 July 2016 at 21:24:04 UTC, Walter Bright wrote: On 7/7/2016 5:56 PM, deadalnix wrote: While this very true, it is clear that most D's complexity doesn't come from there. D's complexity come for the most part from things being

Dub recursive build and forcing pre-build commands to run

I have two questions. 1. Is it possible to build subpackages when dub build is invoked for the main package? It's a pain to first do dub build :mysubpackage and then dub build. 2. It seems that when dub detects that no dependencies need to be updated, it does not run the pre-build commands.

Re: Go's march to low-latency GC

On Friday, 8 July 2016 at 20:35:05 UTC, Martin Nowak wrote: On 07/08/2016 07:45 AM, ikod wrote: Correct me if I'm wrong, but in D fibers allocate stack statically, so we have to preallocate large stacks. If yes - can we allocate stack frames on demand from some non-GC area? Fiber stacks

Re: Battle-plan for CTFE

On Friday, 8 July 2016 at 12:17:29 UTC, Rene Zwanenburg wrote: On Friday, 8 July 2016 at 11:32:10 UTC, Stefan Koch wrote: I forgot to mention I posted a short article about the CTFE design on my blog. https://codesoldier.blogspot.com Feel free to comment or give suggestions. Thanks! Posts

[Issue 16254] [REG 2.072-devel] wrong switch skips initialization error with mixed in case labels

https://issues.dlang.org/show_bug.cgi?id=16254 --- Comment #1 from github-bugzi...@puremagic.com --- Commits pushed to master at https://github.com/dlang/dmd https://github.com/dlang/dmd/commit/fdf70df83495542b9829a2853d0b1c6ee58d83ea fix Issue 16254 - switch skips initialization error -

[Issue 16254] [REG 2.072-devel] wrong switch skips initialization error with mixed in case labels

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

Re: Using information from the dlang sit

On Friday, 8 July 2016 at 07:32:30 UTC, celavek wrote: On Thursday, 7 July 2016 at 14:14:01 UTC, Seb wrote: Your project (an open source platform for programming exercises) looks very nice. I don't see any problem in using information from dlang.org - especially for teaching D to newcomers.

Re: Vision document for H2 2016

On Thursday, 7 July 2016 at 19:56:29 UTC, Andrei Alexandrescu wrote: On 07/07/2016 03:55 PM, Andrei Alexandrescu wrote: https://wiki.dlang.org/Vision/2016H2 -- Andrei Please provide feedback. We'll make a couple more passes before this is complete. Thanks! -- Andrei This list is full of

Variadic Tuple of Structs with Mixed Types

I'm trying to create a tuple of variadic length containing structs with mixed types. So for instance, given struct Foo(T, U) { T x; U y; } I want to create something like Tuple!(Foo!(type1, type2), Foo!(type1, type3), ..., Foo!(type1, typeN)) x; The bar function (below) is

Re: D is crap

On Friday, 8 July 2016 at 21:53:58 UTC, Ola Fosheim Grøstad wrote: On Friday, 8 July 2016 at 12:46:03 UTC, Chris wrote: As for GC, it's hard to tell. When D was actually (not hypothetically) created, GC was _the_ big thing. Java had just taken off, people were pissed off with C/C++,

Re: Vision for the D language - stabilizing complexity?

On Friday, 8 July 2016 at 21:24:04 UTC, Walter Bright wrote: On 7/7/2016 5:56 PM, deadalnix wrote: While this very true, it is clear that most D's complexity doesn't come from there. D's complexity come for the most part from things being completely unprincipled and lack of vision. All

Re: D is crap

On Friday, 8 July 2016 at 12:46:03 UTC, Chris wrote: As for GC, it's hard to tell. When D was actually (not hypothetically) created, GC was _the_ big thing. Java had just taken off, people were pissed off with C/C++, programming and coding was becoming more and more common. Errr... Garbage

Re: D is crap

On Friday, 8 July 2016 at 21:26:19 UTC, Walter Bright wrote: Only on Windows, and that's a common source of frustration for me :( Linux too. Not by default, right? Only with the magic import and call. That's certainly better than on OS X, where there's no segfault handler at all (I don't

Re: Vision for the D language - stabilizing complexity?

On 08.07.2016 21:26, Andrei Alexandrescu wrote: Where is the reference to Walter's promotion of UB in @safe code? Only found this, but IIRC, there was another discussion: http://www.digitalmars.com/d/archives/digitalmars/D/C_compiler_vs_D_compiler_272670.html#N272689

Re: DConf Videos

On Tuesday, 7 June 2016 at 04:25:42 UTC, Mike Parker wrote: On Monday, 6 June 2016 at 18:48:30 UTC, Karabuta wrote: On Monday, 6 June 2016 at 16:22:18 UTC, Gary Willoughby wrote: On Monday, 6 June 2016 at 10:40:01 UTC, sarn wrote: What's the best source of DConf videos at the moment? Are

Re: D is crap

On 7/8/2016 8:17 AM, Luís Marques wrote: On Sunday, 3 July 2016 at 06:23:05 UTC, Walter Bright wrote: If the program is compiled with -g and it crashes (seg faults) you'll usually at least get a stack trace. Running it under a debugger will get you much more information. Only on Windows, and

Re: Vision document for H2 2016

On Thursday, 7 July 2016 at 19:55:51 UTC, Andrei Alexandrescu wrote: https://wiki.dlang.org/Vision/2016H2 -- Andrei Promote video tutorials? :)

Re: Vision for the D language - stabilizing complexity?

On 7/7/2016 5:56 PM, deadalnix wrote: While this very true, it is clear that most D's complexity doesn't come from there. D's complexity come for the most part from things being completely unprincipled and lack of vision. All useful computer languages are unprincipled and complex due to a

Re: Vision for the D language - stabilizing complexity?

On 08.07.2016 04:25, Andrew Godfrey wrote: Another example is "return" used for monads in eg Haskell - even if it only has one meaning in Haskell, it is too mixed up with a different meaning in other common languages. D's "static if" - which is a killer feature if I ignore the keyword - gives

Re: Vision for the D language - stabilizing complexity?

On 07/08/2016 08:42 PM, deadalnix wrote: It is meaningless because sometime, you have A and B that are both safe on their own, but doing both is unsafe. In which case A or B need to be banned, but nothing allows to know which one. Would you mind giving an example? Purely to educate me. This

Re: Vision for the D language - stabilizing complexity?

On 7/7/2016 7:25 PM, Andrew Godfrey wrote: "static" is a terribly non-descriptive name That's why it's the go-to keyword for any functionality we can't think of a good name for, or if the name would be too long such as "launch_nucular_missiles".

Re: First dmd nightly shipping with dub

On 07/08/2016 11:22 AM, Dicebot wrote: > On Friday, 8 July 2016 at 09:13:08 UTC, Martin Nowak wrote: >> What would be the use-case for those? Using newer dub versions with an >> older compiler? > > Or simply using dub with ldc/gdb without also installing dmd. That actually indicates that

Re: Vision document for H2 2016

On 7/8/2016 7:01 AM, Eugene wrote: please add some features from Rust: primitive type aliases, like i8, u8, u32, and so on http://dlang.org/phobos/core_stdc_stdint.html

Re: Vision document for H2 2016

On 7/8/2016 6:51 AM, Robert M. Münch wrote: 1. Fixing (all) bugs before doing new things: If I look as a CTO, CIO or CEO on D I the first thing I ask is: "Are they doing a lot of new stuff? And if, is this thing / last releasae that bullet proof stable that there are not annoying open issued?"

Re: Go's march to low-latency GC

On 07/08/2016 07:45 AM, ikod wrote: > Correct me if I'm wrong, but in D fibers allocate stack statically, so > we have to preallocate large stacks. > > If yes - can we allocate stack frames on demand from some non-GC area? Fiber stacks are just mapped virtual memory pages that the kernel only

[Issue 16254] New: [REG 2.072-devel] wrong switch skips initialization error with mixed in case labels

https://issues.dlang.org/show_bug.cgi?id=16254 Issue ID: 16254 Summary: [REG 2.072-devel] wrong switch skips initialization error with mixed in case labels Product: D Version: D2 Hardware: All OS: All

Re: Vision for the D language - stabilizing complexity?

On Fri, Jul 08, 2016 at 08:01:10PM +, Stefan Koch via Digitalmars-d wrote: > On Friday, 8 July 2016 at 19:43:39 UTC, jmh530 wrote: > > On Friday, 8 July 2016 at 18:16:03 UTC, Andrei Alexandrescu wrote: > > > > > > You may well be literally the only person on Earth who dislikes > > > the use

Re: Different function attributes between debug and release build

On Thursday, 7 July 2016 at 19:39:12 UTC, Lodovico Giaretta wrote: Currently, std.string.assumeUTF is inferred @nogc in release mode, while in debug mode it isn't. Should this be allowed? It can cause some problems, e.g. I have some @nogc unittests that I use to guarantee that my code is in

Re: Vision for the D language - stabilizing complexity?

On Friday, 8 July 2016 at 19:43:39 UTC, jmh530 wrote: On Friday, 8 July 2016 at 18:16:03 UTC, Andrei Alexandrescu wrote: You may well be literally the only person on Earth who dislikes the use of "static" in "static if". -- Andrei You have to admit that static is used in a lot of different

Re: Vision for the D language - stabilizing complexity?

On Friday, 8 July 2016 at 18:16:03 UTC, Andrei Alexandrescu wrote: You may well be literally the only person on Earth who dislikes the use of "static" in "static if". -- Andrei You have to admit that static is used in a lot of different places in D. It doesn't always mean something like

[Issue 16244] compiler ICE on complex `typeof()` for method arg type

https://issues.dlang.org/show_bug.cgi?id=16244 Ketmar Dark changed: What|Removed |Added CC|

Re: Vision for the D language - stabilizing complexity?

On 07/08/2016 02:42 PM, deadalnix wrote: It is meaningless because sometime, you have A and B that are both safe on their own, but doing both is unsafe. In which case A or B need to be banned, but nothing allows to know which one. This isn't a bug, this is a failure to have a principled approach

Re: Vision for the D language - stabilizing complexity?

On Friday, 8 July 2016 at 05:26:44 UTC, ag0aep6g wrote: And so on, @safe only mean safe if you do not do this and that, As far as I'm aware, the dictatorship agrees that the holes in @safe are bugs that need fixing. That's a completely meaningless statement, plus overall the dictatorship

Re: D is crap

p.s. it's not something specifical to D. any program that "catches" segfault by itself should be burnt with fire.

Re: D is crap

On Friday, 8 July 2016 at 17:04:04 UTC, Luís Marques wrote: On Friday, 8 July 2016 at 15:31:53 UTC, ketmar wrote: core.exception.AssertError@z00.d(2): BOOM! what am i doing wrong? O_O That's an exception, not a segfault. Try something like int* x; *x = 42; segfault is

Re: Vision document for H2 2016

On 07/07/2016 03:55 PM, Andrei Alexandrescu wrote: https://wiki.dlang.org/Vision/2016H2 -- Andrei I have integrated https://wiki.dlang.org/Walter_Andrei_Action_List#Walter_and_Andrei.27s_Action_List within https://wiki.dlang.org/Vision/2016H2. Andrei

Re: Vision for the D language - stabilizing complexity?

On 07/07/2016 10:25 PM, Andrew Godfrey wrote: D's "static if" - which is a killer feature if I ignore the keyword - gives me a similar feeling (though it's much less egregious than "return" in monads). "static" is a terribly non-descriptive name because there are so many senses in which a thing

Re: Vision document for H2 2016

On 07/08/2016 01:04 PM, Jack Stouffer wrote: On Friday, 8 July 2016 at 16:55:54 UTC, Andrei Alexandrescu wrote: I think the most important concrete step is to find more reviewers, which is already in the document. As to how to do that, I'm not sure. -- Andrei To be blunt, the vision (and

Re: Vision document for H2 2016

On 07/08/2016 12:04 PM, Andrew Godfrey wrote: 1) A link to that action list, placing it in context relative to this doc, and encouraging people to add their ideas like "rust aliases" there instead of here. (Or maybe you have a better place for this, like a forum where such requests are discussed

Re: Vision document for H2 2016

On 07/08/2016 09:51 AM, Robert M. Münch wrote: 1. Fixing (all) bugs before doing new things: If I look as a CTO, CIO or CEO on D I the first thing I ask is: "Are they doing a lot of new stuff? And if, is this thing / last releasae that bullet proof stable that there are not annoying open

Re: Vision document for H2 2016

On 07/08/2016 10:01 AM, Eugene wrote: On Thursday, 7 July 2016 at 19:55:51 UTC, Andrei Alexandrescu wrote: https://wiki.dlang.org/Vision/2016H2 -- Andrei please add some features from Rust: primitive type aliases, like i8, u8, u32, and so on No need. -- Andrei

Re: Vision document for H2 2016

On 07/08/2016 05:17 AM, Robert burner Schadek wrote: On Thursday, 7 July 2016 at 20:44:05 UTC, Andrei Alexandrescu wrote: On 7/7/16 3:55 PM, Andrei Alexandrescu wrote: https://wiki.dlang.org/Vision/2016H2 -- Andrei In the next pass I will integrate Walter_Andrei_Action_List I'm quite

[Issue 16231] Language specification: rename std.regexp -> std.regex

https://issues.dlang.org/show_bug.cgi?id=16231 --- Comment #1 from github-bugzi...@puremagic.com --- Commits pushed to master at https://github.com/dlang/dlang.org https://github.com/dlang/dlang.org/commit/5dd6ee324cb11b21870960ad446d083301355751 fix issue 16231 - Language spec: rename

[Issue 16253] BitmappedBlock allocator not working with chooseAtRuntime

https://issues.dlang.org/show_bug.cgi?id=16253 Lodovico Giaretta changed: What|Removed |Added CC|

[Issue 16253] New: BitmappedBlock allocator not working with chooseAtRuntime

https://issues.dlang.org/show_bug.cgi?id=16253 Issue ID: 16253 Summary: BitmappedBlock allocator not working with chooseAtRuntime Product: D Version: D2 Hardware: All OS: All Status: NEW

Re: D is crap

On Friday, 8 July 2016 at 16:08:42 UTC, bachmeier wrote: Yep. If you're going to pick any feature to use to sell a new language, lack of GC is the worst. The only ones that care (and it's a small percentage) are the ones that are least likely to switch due to their existing tools, libraries,

Re: Vision document for H2 2016

On 07/08/2016 12:00 AM, rikki cattermole wrote: On 08/07/2016 7:55 AM, Andrei Alexandrescu wrote: https://wiki.dlang.org/Vision/2016H2 -- Andrei We really need opRef* implemented in dmd. What is that? -- Andrei

Re: Vision document for H2 2016

On 07/08/2016 02:54 AM, Johannes Pfau wrote: Am Thu, 7 Jul 2016 15:55:51 -0400 schrieb Andrei Alexandrescu : https://wiki.dlang.org/Vision/2016H2 -- Andrei Safety and Memory Management Btw: You said #15951 (Inefficiencies in struct initialization) is a

Re: Vision document for H2 2016

On 07/07/2016 06:06 PM, qznc wrote: On Thursday, 7 July 2016 at 19:56:29 UTC, Andrei Alexandrescu wrote: On 07/07/2016 03:55 PM, Andrei Alexandrescu wrote: https://wiki.dlang.org/Vision/2016H2 -- Andrei Please provide feedback. We'll make a couple more passes before this is complete. Thanks!

Re: D is crap

On Friday, 8 July 2016 at 15:30:12 UTC, Schrom, Brian T wrote: I've had reasonable success using lldb on mac. I was referring to the stack trace on segfault, but regarding the user of debuggers on a Mac with D, most of the time it doesn't work very well for me. I think last time I used lldb

Re: Vision document for H2 2016

On 07/07/2016 05:48 PM, Seb wrote: On Thursday, 7 July 2016 at 19:56:29 UTC, Andrei Alexandrescu wrote: On 07/07/2016 03:55 PM, Andrei Alexandrescu wrote: https://wiki.dlang.org/Vision/2016H2 -- Andrei Please provide feedback. We'll make a couple more passes before this is complete. Thanks!

Re: Vision document for H2 2016

On Friday, 8 July 2016 at 16:55:54 UTC, Andrei Alexandrescu wrote: I think the most important concrete step is to find more reviewers, which is already in the document. As to how to do that, I'm not sure. -- Andrei To be blunt, the vision (and goals in general) are kind of useless without a

Re: D is crap

On Friday, 8 July 2016 at 16:08:42 UTC, bachmeier wrote: On Friday, 8 July 2016 at 12:46:03 UTC, Chris wrote: As for GC, it's hard to tell. When D was actually (not hypothetically) created, GC was _the_ big thing. Java had just taken off, people were pissed off with C/C++, programming and

Re: D is crap

On Friday, 8 July 2016 at 15:31:53 UTC, ketmar wrote: core.exception.AssertError@z00.d(2): BOOM! what am i doing wrong? O_O That's an exception, not a segfault. Try something like int* x; *x = 42;

Re: Vision document for H2 2016

On 07/07/2016 04:39 PM, H. S. Teoh via Digitalmars-d-announce wrote: On Thu, Jul 07, 2016 at 03:55:51PM -0400, Andrei Alexandrescu via Digitalmars-d-announce wrote: https://wiki.dlang.org/Vision/2016H2 -- Andrei Under "raising participation", are there any concrete steps that can be taken to

Re: D is crap

On 7/8/16 8:22 AM, Luís Marques via Digitalmars-d wrote: > On Sunday, 3 July 2016 at 06:23:05 UTC, Walter Bright wrote: >> If the program is compiled with -g and it crashes (seg faults) >> you'll usually at least get a stack trace. Running it under a >> debugger will get you much more

Re: Logical location of template instantiations

On Friday, July 08, 2016 15:08:35 Timon Gehr via Digitalmars-d wrote: > On 08.07.2016 09:45, Jonathan M Davis via Digitalmars-d wrote: > > On Thursday, July 07, 2016 23:20:28 Timon Gehr via Digitalmars-d wrote: > >> On 07.07.2016 17:11, Jonathan M Davis via Digitalmars-d wrote: > >>>So, > >>>

Re: D is crap

On Friday, 8 July 2016 at 12:46:03 UTC, Chris wrote: As for GC, it's hard to tell. When D was actually (not hypothetically) created, GC was _the_ big thing. Java had just taken off, people were pissed off with C/C++, programming and coding was becoming more and more common. Not having GC

Re: Vision document for H2 2016

On Fri, Jul 08, 2016 at 09:17:14AM +, Robert burner Schadek via Digitalmars-d-announce wrote: [...] > I'm not the much in the DMD process, but what about making the > frontend a library and being able to select the backend at the time of > compilation, as shortly mentioned at DConf. I bet

[Issue 15354] unstable operator overloading with mixin expression

https://issues.dlang.org/show_bug.cgi?id=15354 Artem Borisovskiy changed: What|Removed |Added CC||kolo...@bk.ru ---

Re: Vision document for H2 2016

On Thursday, 7 July 2016 at 19:55:51 UTC, Andrei Alexandrescu wrote: https://wiki.dlang.org/Vision/2016H2 -- Andrei I see that this thread has sparked a lot of "ideas for the future". That's a great outcome but many of them don't belong in this vision document, and in fact some probably

Re: D is crap

On Friday, 8 July 2016 at 15:17:33 UTC, Luís Marques wrote: On Sunday, 3 July 2016 at 06:23:05 UTC, Walter Bright wrote: If the program is compiled with -g and it crashes (seg faults) you'll usually at least get a stack trace. Running it under a debugger will get you much more information.

Re: D is crap

On Sunday, 3 July 2016 at 06:23:05 UTC, Walter Bright wrote: If the program is compiled with -g and it crashes (seg faults) you'll usually at least get a stack trace. Running it under a debugger will get you much more information. Only on Windows, and that's a common source of frustration for

Re: Vision document for H2 2016

On Friday, 8 July 2016 at 14:01:14 UTC, Eugene wrote: On Thursday, 7 July 2016 at 19:55:51 UTC, Andrei Alexandrescu wrote: https://wiki.dlang.org/Vision/2016H2 -- Andrei please add some features from Rust: primitive type aliases, like i8, u8, u32, and so on Not hard: module stdrust;

[Issue 16028] Incorrect cache size returned from core.cpuid

https://issues.dlang.org/show_bug.cgi?id=16028 Илья Ярошенко changed: What|Removed |Added CC|

Re: Vision for the D language - stabilizing complexity?

On Friday, 8 July 2016 at 00:56:25 UTC, deadalnix wrote: While this very true, it is clear that most D's complexity doesn't come from there. D's complexity come for the most part from things being completely unprincipled and lack of vision. But that way is PRAGMATIC, don't you know about

Re: Vision document for H2 2016

On Thursday, 7 July 2016 at 19:55:51 UTC, Andrei Alexandrescu wrote: https://wiki.dlang.org/Vision/2016H2 -- Andrei please add some features from Rust: primitive type aliases, like i8, u8, u32, and so on

Re: Vision document for H2 2016

On 2016-07-07 19:55:51 +, Andrei Alexandrescu said: https://wiki.dlang.org/Vision/2016H2 -- Andrei A more "business / managment" view: If we want to achieve hihger adoption rate of D, which IMO should be the first priority as it's an enabler for a lot of the other things posted, the

Re: Vision document for H2 2016

On Friday, 8 July 2016 at 09:17:14 UTC, Robert burner Schadek wrote: You create a VD roughly twice a year. You have to compare it with the last VD and see what was done. That is a lot of overhead IMO. Why not create "THE VISION DOCUMENT" and update it when needed. I like to think about it

Re: Logical location of template instantiations

On 08.07.2016 09:45, Jonathan M Davis via Digitalmars-d wrote: On Thursday, July 07, 2016 23:20:28 Timon Gehr via Digitalmars-d wrote: On 07.07.2016 17:11, Jonathan M Davis via Digitalmars-d wrote: So, the buck would have to be passed at every point that the symbol were passed as an alias

Re: D is crap

On Friday, 8 July 2016 at 01:17:55 UTC, Luís Marques wrote: Sometimes I idly wonder what would have happened if D were available in the 80's. Sort of like if you put a modern car for sale in the 1960's. I've also thought about that from time to time. I think D would have been very

Re: Battle-plan for CTFE

On Friday, 8 July 2016 at 11:32:10 UTC, Stefan Koch wrote: I forgot to mention I posted a short article about the CTFE design on my blog. https://codesoldier.blogspot.com Feel free to comment or give suggestions. Thanks! Posts like these are always interesting to read. I noticed a few

Re: Second class pointers

On Friday, 8 July 2016 at 11:05:36 UTC, ZombineDev wrote: On Friday, 8 July 2016 at 06:17:43 UTC, Nicholas Wilson wrote: On Friday, 8 July 2016 at 05:53:21 UTC, Nicholas Wilson wrote: So as part of my effort to get D running on GPUs I need to make a "second class" pointer type that I can alter

Re: Battle-plan for CTFE

On Thursday, 7 July 2016 at 17:47:28 UTC, Stefan Koch wrote: On Thursday, 7 July 2016 at 13:55:44 UTC, Stefan Koch wrote: I just made a PR to fix it for ctfe. It's a hack but then again ... The whole handling of PowExp is a hack. Clarification now it works on Literals. It is still not

Re: Second class pointers

On Friday, 8 July 2016 at 06:17:43 UTC, Nicholas Wilson wrote: On Friday, 8 July 2016 at 05:53:21 UTC, Nicholas Wilson wrote: So as part of my effort to get D running on GPUs I need to make a "second class" pointer type that I can alter in the backend of LDC to the correct address space. to

Re: First dmd nightly shipping with dub

On Friday, 8 July 2016 at 09:13:08 UTC, Martin Nowak wrote: What would be the use-case for those? Using newer dub versions with an older compiler? Or simply using dub with ldc/gdb without also installing dmd.

[Issue 16252] Region allocator should not be copyable

https://issues.dlang.org/show_bug.cgi?id=16252 Lodovico Giaretta changed: What|Removed |Added CC|

[Issue 16252] New: Region allocator should not be copyable

https://issues.dlang.org/show_bug.cgi?id=16252 Issue ID: 16252 Summary: Region allocator should not be copyable Product: D Version: D2 Hardware: All OS: All Status: NEW Severity: enhancement

Re: Vision document for H2 2016

On Thursday, 7 July 2016 at 20:44:05 UTC, Andrei Alexandrescu wrote: On 7/7/16 3:55 PM, Andrei Alexandrescu wrote: https://wiki.dlang.org/Vision/2016H2 -- Andrei In the next pass I will integrate Walter_Andrei_Action_List I'm quite underwhelmed by the Vision Document (VD). I think that is

Re: First dmd nightly shipping with dub

On Wednesday, 6 July 2016 at 14:32:45 UTC, Dejan Lekic wrote: Good work! I presume the "independent" dub packages will also be available, right? What would be the use-case for those? Using newer dub versions with an older compiler?

Re: local const functions - bug ?

On Thursday, 7 July 2016 at 15:02:29 UTC, Jonathan M Davis wrote: On Thursday, July 07, 2016 10:33:39 Basile B. via Digitalmars-d-learn wrote: this compiles without error: struct Foo { int i; void bar() { void foo() const { i = 1; }

Re: BulletD needs your help!

On Monday, 4 July 2016 at 20:03:45 UTC, BLM768 wrote: Thoughts? Concerns? Tomatoes? Hey there, I'm sad this post hasn't called anyone's attention so far. While I am defintely interested to have BulletD become a thing, I sadly can't collaborate with it so far. It's been on my mind to give

Re: Blocking points for further D adoption

It's been suggested that DMD/LDC/GDC could be combined into a bundle, say DCC, and when you call DCC hello.d it will call dmd hello.d, and if you call DCC -fast hello.d it will call ldc hello.d or gdc hello.d This will give newcomers a different experience. I'm wondering if you couldn't

Re: Logical location of template instantiations

On Thursday, July 07, 2016 23:20:28 Timon Gehr via Digitalmars-d wrote: > On 07.07.2016 17:11, Jonathan M Davis via Digitalmars-d wrote: > > So, > > > > the buck would have to be passed at every point that the symbol were > > passed > > as an alias argument such that the check for accessibility

Re: Using information from the dlang sit

On Thursday, 7 July 2016 at 14:14:01 UTC, Seb wrote: Your project (an open source platform for programming exercises) looks very nice. I don't see any problem in using information from dlang.org - especially for teaching D to newcomers. Most of the content is licensed under the Boost

Re: opOpAssign

On Friday, 8 July 2016 at 07:15:06 UTC, ketmar wrote: auto opOpAssign(string op)(ptrdiff_t i) if(op =="+" || op == "-") Derp. Thanks!

Re: opOpAssign

auto opOpAssign(string op)(ptrdiff_t i) if(op =="+" || op == "-")

opOpAssign

struct Pointer(uint p, T) if(p <= Generic) { T* ptr; ref T opUnary(string op)() if(op=="*") { return *ptr; } ref T opIndex(size_t i) { return *(ptr+i); } auto opBinary(string op)(ptrdiff_t i) if(op == "+" || op == "-") { return

  1   2   >