Jump to page: 1 25  
Page
Thread overview
Vision document for H2 2016
Jul 07, 2016
Seb
Jul 07, 2016
qznc
Jul 08, 2016
Carl Vogel
Jul 07, 2016
H. S. Teoh
Jul 07, 2016
Walter Bright
Jul 07, 2016
Brad Roberts
Jul 08, 2016
Martin Nowak
Jul 07, 2016
H. S. Teoh
Jul 08, 2016
Jack Stouffer
Jul 08, 2016
jmh530
Jul 08, 2016
H. S. Teoh
Jul 10, 2016
Jacob Carlborg
Jul 20, 2016
tsbockman
Jul 08, 2016
rikki cattermole
Jul 09, 2016
rikki cattermole
Jul 08, 2016
Johannes Pfau
Jul 08, 2016
Robert M. Münch
Jul 09, 2016
Robert M. Münch
Jul 08, 2016
Walter Bright
Jul 09, 2016
Robert M. Münch
Jul 08, 2016
Eugene
Jul 08, 2016
jmh530
Jul 08, 2016
Walter Bright
Jul 08, 2016
Andrew Godfrey
Jul 08, 2016
Karabuta
Jul 09, 2016
Eugene
Jul 10, 2016
Chris Wright
Jul 14, 2016
Javier
July 07, 2016
https://wiki.dlang.org/Vision/2016H2 -- Andrei
July 07, 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
July 07, 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 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&list_id=209407&resolution=---

The @safe cheesegrater still has (quite) a few more holes to plug.


T

-- 
Gone Chopin. Bach in a minuet.
July 07, 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 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&list_id=209407&resolution=---
>
> 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

July 07, 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 a couple releases, but the list did get down to just 1 that was deemed not blocking (I don't remember the details).
July 07, 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 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
July 07, 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 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
July 07, 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 need to cut down on overhead and bureaucracy. Last thing we want is yet another document to maintain. -- Andrei

July 07, 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 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)
July 07, 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&list_id=209407&resolution=---
>
> 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&bug_status=ASSIGNED&bug_status=REOPENED&keywords=safe&keywords_type=allwords&list_id=209410&query_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.
« First   ‹ Prev
1 2 3 4 5