On Wednesday, 14 June 2017 at 12:53:21 UTC, MysticZach wrote:
On Wednesday, 14 June 2017 at 12:17:50 UTC, Mike Parker wrote:
In this thread, I'm specifically looking for feedback on my
updates to the readme and the guidelines. Sorry for any
confusion.
s/GUIDLINES.md/GUIDELINES.md/
In the
On Wednesday, 14 June 2017 at 12:17:50 UTC, Mike Parker wrote:
In this thread, I'm specifically looking for feedback on my
updates to the readme and the guidelines. Sorry for any
confusion.
s/GUIDLINES.md/GUIDELINES.md/
On Wednesday, 14 June 2017 at 10:41:01 UTC, MysticZach wrote:
On Wednesday, 14 June 2017 at 10:32:50 UTC, Andre Pany wrote:
[3] https://github.com/dlang/DIPs/pull/71
Hi,
the work on this dip is highly appreciated. For my AWS SDK
this DIP would
make the coding much more readable and also
On Wednesday, 14 June 2017 at 10:32:50 UTC, Andre Pany wrote:
[3] https://github.com/dlang/DIPs/pull/71
Hi,
the work on this dip is highly appreciated. For my AWS SDK this
DIP would
make the coding much more readable and also smaller for several
use cases.
At this point in the process,
On Monday, 12 June 2017 at 17:51:05 UTC, Mike Parker wrote:
Now that I've got a few DIP reviews under my belt, I've got a
good enough handle on the process to lay it out in
documentation form. To that end [1], I've kept the general
structure that Dicebot initially set down, changing the
On Monday, 12 June 2017 at 17:51:05 UTC, Mike Parker wrote:
Now that I've got a few DIP reviews under my belt, I've got a
good enough handle on the process to lay it out in
documentation form. To that end [1], I've kept the general
structure that Dicebot initially set down, changing the
Now that I've got a few DIP reviews under my belt, I've got a
good enough handle on the process to lay it out in documentation
form. To that end [1], I've kept the general structure that
Dicebot initially set down, changing the details to better
reflect my view of how it should all work (I
