DIP 1017--Add Bottom Type--Final Review

Meta jared771 at gmail.com
Tue Jan 15 18:40:18 UTC 2019


On Tuesday, 15 January 2019 at 18:36:30 UTC, Neia Neutuladh wrote:
> Agreed. DIPs should use simple language and aim to use examples 
> whenever possible. Brevity and sounding technical should be 
> explicit non-goals.

+1

IMO, part of the DIP requirements should be that they are written 
as simply as possible with minimal use of jargon. That's just 
good sense, though, because people will not be accepting of a DIP 
that they can't grok.


More information about the Digitalmars-d mailing list