Re: Vision document for H2 2016

On 08/07/2016 7:55 AM, Andrei Alexandrescu wrote: https://wiki.dlang.org/Vision/2016H2 -- Andrei We really need opRef* implemented in dmd.

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 Wrt "Improve

Re: Vision document for H2 2016

On 7/7/2016 1:16 PM, H. S. Teoh via Digitalmars-d-announce wrote: Recently Walter has been fixing a series of compiler bugs related to @safe, which is a very promising development, but we're not quite there yet: https://issues.dlang.org/buglist.cgi?keywords=safe_id=209407=--- The

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 I agree that you should

Re: Vision document for H2 2016

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 realize this goal? Given that last quarter we failed to achieve the

Re: Vision document for H2 2016

On 7/7/16 3:55 PM, Andrei Alexandrescu wrote: https://wiki.dlang.org/Vision/2016H2 -- Andrei In the next pass I will integrate https://wiki.dlang.org/Walter_Andrei_Action_List#Walter_and_Andrei.27s_Action_List within the vision document. We're already stretched thin organizationally, and

Re: Vision document for H2 2016

On 7/7/16 4:33 PM, Brad Roberts via Digitalmars-d-announce wrote: On 7/7/16 12:55 PM, Andrei Alexandrescu via Digitalmars-d-announce wrote: https://wiki.dlang.org/Vision/2016H2 -- Andrei In the release management section, I'd like to see some priority placed on regressions. There was a time

Re: Vision document for H2 2016

On 7/7/16 4:16 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 "safety and memory management", what about adding "plug existing known

Re: Vision document for H2 2016

On 7/7/16 12:55 PM, Andrei Alexandrescu via Digitalmars-d-announce wrote: https://wiki.dlang.org/Vision/2016H2 -- Andrei In the release management section, I'd like to see some priority placed on regressions. There was a time that releases were held until those where addressed. It was only

Re: Vision document for H2 2016

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 "safety and memory management", what about adding "plug existing known loopholes in @safe"? Recently Walter has been fixing a series of compiler

Re: Vision document for H2 2016

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

Vision document for H2 2016

https://wiki.dlang.org/Vision/2016H2 -- Andrei

intel-intrinsics package, use Intel syntax for SIMD intrinsics

The idea behind this (LDC-only) package is to reuse the existing body of code and documentation that exist for C++ programmers, using the Intel x86 intrinsics name. Available through DUB: http://code.dlang.org/packages/intel-intrinsics While the syntax and portability are worse than vanilla

Re: Battle-plan for CTFE

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 available at ctfe and the full non-hackish fix will take a while.

Re: Project Highlight: Auburn Sounds

On Thursday, 7 July 2016 at 13:32:03 UTC, Mike Parker wrote: Guillaume Piolat (a.k.a p0nce) talks a little bit on the D Blog [1] about using D for his Auburn Sounds audio plugins[2]. [1] https://dlang.org/blog/2016/07/07/project-highlight-auburn-sounds/ [2] https://www.auburnsounds.com/

Re: Battle-plan for CTFE

On Tuesday, 10 May 2016 at 00:36:21 UTC, Walter Bright wrote: On 5/9/2016 2:32 PM, Andrej Mitrovic via Digitalmars-d-announce wrote: On 5/9/16, Stefan Koch via Digitalmars-d-announce wrote: I was shocked to discover that the PowExpression actually depends

Re: Project Highlight: Auburn Sounds

On Thursday, 7 July 2016 at 13:32:03 UTC, Mike Parker wrote: Guillaume Piolat (a.k.a p0nce) talks a little bit on the D Blog [1] about using D for his Auburn Sounds audio plugins[2]. [1] https://dlang.org/blog/2016/07/07/project-highlight-auburn-sounds/ [2] https://www.auburnsounds.com/

Project Highlight: Auburn Sounds

Guillaume Piolat (a.k.a p0nce) talks a little bit on the D Blog [1] about using D for his Auburn Sounds audio plugins[2]. [1] https://dlang.org/blog/2016/07/07/project-highlight-auburn-sounds/ [2] https://www.auburnsounds.com/

Re: Battle-plan for CTFE

yay. ackemann(3, 7) in 70 milliseconds! and it does TCO. default interpreter is unable to execute that -- recursion is too deep.

Re: dlang-requests 0.2.0 released

On Wednesday, 6 July 2016 at 20:58:19 UTC, ikod wrote: Hello, dlang-requests v0.2.0 released. Major feature improvement: 1. Nonblocking vibe.d sockets support. That means you can safely use dlang-requests in vibe.d applications. Thanks to Johannes Pfau (https://github.com/jpf91). Minor