Re: Vision document for H2 2016

[rikki cattermole via Digitalmars-d-announce]

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

[qznc via Digitalmars-d-announce]

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 organization": I see a lot of potential in 
automating more stuff.


* Have a bot for pinging reviewers like Facebook's mention-bot or 
Rust's highfive


* Check various Phobos guidelines like "every function must have 
an example"


* Use dfmt on Phobos (I know this is much bigger than it sounds)

* Compile all dub packages for testing

* Track performance and memory use

* Have a blog post about the automation we already have 
(autotester deserves some applause once in while)


The nice thing about automating stuff is that it usually pays off 
the investment in the long run. ;)

Re: Vision document for H2 2016

[Walter Bright via Digitalmars-d-announce]

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 @safe cheesegrater still has (quite) a few more holes to plug.



Most of those are resolved. Here's a better link:

https://issues.dlang.org/buglist.cgi?bug_status=NEW_status=ASSIGNED_status=REOPENED=safe_type=allwords_id=209410_format=advanced

19 of which are in DMD, down from around 40 a month ago. The remainder are 
mostly due to 'scope' not being implemented.

Re: Vision document for H2 2016

[Seb via Digitalmars-d-announce]

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 explain how it is planned to achieve 
"Raising participation". Here's an idea:


Create an outreach/PR team, with the following tasks

a) "Recruitment"
---

- Issue official press releases from the D foundation for major 
milestones and releases

- Improve the newcomer experience (aka your first five minutes)
- Find ways to inspire developers to get more in touch and 
inspire their community
- Find sponsors/members organizations for the D foundation once 
it's official
- Help and encourage others to create online course & learning 
material about D
- Reach out to interested universities and assist them in their 
leading role


See also: http://dlang.org/areas-of-d-usage.html#teaching

b) Brand awareness
--

- consider to use the new design from the DConf16
- provide (or better: sell) small branding items (stickers, 
posters, T-shirts, ...)
- make the #DlangMan culture more mainstream (atm it's mostly 
Japanese)


Another main point that I couldn't see at the moment is:

User experience
---

- better error messages & diagnostics (e.g. DIP83)
- afaik macOS still doesn't show line numbers
- create a Dlang survey (like the Rust survey) for feedback (e.g. 
with PR group from above)

Re: Vision document for H2 2016

[H. S. Teoh via Digitalmars-d-announce]

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 target number of PRs, it seems that specifying more concrete steps
would be a first step to actually reaching the goal, instead of merely
hoping things would somehow just come together.


T

-- 
Nearly all men can stand adversity, but if you want to test a man's character, 
give him power. -- Abraham Lincoln

Re: Vision document for H2 2016

[Andrei Alexandrescu via Digitalmars-d-announce]

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 need to cut down on overhead and bureaucracy. Last 
thing we want is yet another document to maintain. -- Andrei

Re: Vision document for H2 2016

[Andrei Alexandrescu via Digitalmars-d-announce]

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 that releases were held until those
where addressed.  It was only a couple releases, but the list did get
down to just 1 that was deemed not blocking (I don't remember the details).


Added a sentence: "Regressions should be paid utmost attention." Thanks! 
-- Andrei

Re: Vision document for H2 2016

[Andrei Alexandrescu via Digitalmars-d-announce]

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 loopholes in @safe"?

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 @safe cheesegrater still has (quite) a few more holes to plug.


Added: "Fix all errors in language design and implementation that allow 
unsafe behavior in @safe code." Thanks! -- Andrei

Re: Vision document for H2 2016

[Brad Roberts via Digitalmars-d-announce]

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 a couple releases, but the 
list did get down to just 1 that was deemed not blocking (I don't remember the details).

Re: Vision document for H2 2016

[H. S. Teoh via Digitalmars-d-announce]

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 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 @safe cheesegrater still has (quite) a few more holes to plug.


T

-- 
Gone Chopin. Bach in a minuet.

Re: Vision document for H2 2016

[Andrei Alexandrescu via Digitalmars-d-announce]

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

[Andrei Alexandrescu via Digitalmars-d-announce]

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

intel-intrinsics package, use Intel syntax for SIMD intrinsics

[Guillaume Piolat via Digitalmars-d-announce]

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 LDC 
vector support, this allows to use the Intel's guide here: 
https://software.intel.com/sites/landingpage/IntrinsicsGuide/


So far the syntax looks pretty much identical with C++ compilers 
like MSVC, clang and ICC - except for the shifts instructions.

Re: Battle-plan for CTFE

[Stefan Koch via Digitalmars-d-announce]

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

[Seb via Digitalmars-d-announce]

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/


Reddit:

https://reddit.com/r/programming/comments/4roj67/d_project_highlight_auburn_sounds/

Re: Battle-plan for CTFE

[Stefan Koch via Digitalmars-d-announce]

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

on phobos!


I seem to remember having to implement diagnostics in DMD 
asking for
the user to import std.math. I'm fairly confident it had 
something to

do with power expressions.

Yah, it's a mess. :)



The pow stuff should just be done in dmd without reference to 
the library.


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.

Re: Project Highlight: Auburn Sounds

[Guillaume Piolat via Digitalmars-d-announce]

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/


Thanks for doing this Michael ;)

Project Highlight: Auburn Sounds

[Mike Parker via Digitalmars-d-announce]

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

[ketmar via Digitalmars-d-announce]

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

[qznc via Digitalmars-d-announce]

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 improvements:
2. Dump network data when verbosity level>=3
3. Throw exception when maxRedirects reached instead of 
returning redirect status code.


dlang-request is D http client library, inspired by 
python-requests.


Project code: https://github.com/ikod/dlang-requests


I'm using 0.1.9 [0] and I'm happy. Thanks!

[0] https://github.com/qznc/d-github