• Max Haughton (3/3) May 30 2019 Are the __traits considered to be part of the specification
• bauss (9/12) May 30 2019 If it's trivial then you probably don't need a DIP for it.
• Basile B. (15/27) May 31 2019 A "light" DIP process for this case is on the way from what I've
• Jacob Carlborg (4/6) Jun 04 2019 In general you do not need a DIP for adding a new __trait.

Max Haughton <maxhaton gmail.com> writes:

Are the __traits considered to be part of the specification 
proper? Do potential new traits need a DIP or do they go straight 
into DMD + website?

bauss <jj_1337 live.dk> writes:

On Friday, 31 May 2019 at 05:29:16 UTC, Max Haughton wrote:
 Are the __traits considered to be part of the specification 
 proper? Do potential new traits need a DIP or do they go 
 straight into DMD + website?

If it's trivial then you probably don't need a DIP for it.

Usually DIPs are for "larger" or "more complex" implementations. 
AFAIK.

I have seen a few new __traits etc. added just with a simple PR 
and no DIP.

If the __traits has any breaking changes etc. then it would most 
likely need a DIP ofc.

-- Anyone can feel free to correct me on this though. --

Basile B. <b2.temp gmx.com> writes:

On Friday, 31 May 2019 at 05:57:58 UTC, bauss wrote:
 On Friday, 31 May 2019 at 05:29:16 UTC, Max Haughton wrote:
 Are the __traits considered to be part of the specification 
 proper? Do potential new traits need a DIP or do they go 
 straight into DMD + website?

 If it's trivial then you probably don't need a DIP for it.

 Usually DIPs are for "larger" or "more complex" 
 implementations. AFAIK.

 I have seen a few new __traits etc. added just with a simple PR 
 and no DIP.

 If the __traits has any breaking changes etc. then it would 
 most likely need a DIP ofc.

 -- Anyone can feel free to correct me on this though. --

A "light" DIP process for this case is on the way from what I've 
read.
I've myself got two changes merged but they were limit toward 
this aspect and there was a bit of confusion because the decision 
makers were not necessarily aware while another member would have 
merged quite quickly.

For now if someone wants to got a simple language change merged 
and since the light DIP is still not there:

1. take case to make it visible in the PR name,
2. request the tags (often those two: [needs approval] [need 
specs pr])
3. ping the right persons, i.e Bright or at least Mike (adalcron) 
and
4. eventually opens a topic in the general section of the forum.

Jacob Carlborg <doob me.com> writes:

On 2019-05-31 07:29, Max Haughton wrote:
 Are the __traits considered to be part of the specification proper? Do 
 potential new traits need a DIP or do they go straight into DMD + website?

In general you do not need a DIP for adding a new __trait.

-- 
/Jacob Carlborg