On Saturday, 24 March 2018 at 04:06:12 UTC, barry wrote:
On Saturday, 24 March 2018 at 00:51:22 UTC, shion wrote:
Github erased me, without any omens / notice, no reply.
So, ShionKeys/, I disappeared on gihub.
You have been deleted. I'd call that a bad omen right there.
Maybe Github saw the
On Saturday, 24 March 2018 at 00:51:22 UTC, shion wrote:
Github erased me, without any omens / notice, no reply.
So, ShionKeys/, I disappeared on gihub.
You have been deleted. I'd call that a bad omen right there.
Maybe Github saw the raw power of what you had created. A
keyboard that may
On Saturday, 24 March 2018 at 01:15:46 UTC, Jonathan M Davis wrote
A number of us have nothing good to say about TDD.
That's fine. That's why they have menus in restaurants. But
saying it is an inferior method is different than saying it won't
work or can't be used in a maintenance
On Saturday, March 24, 2018 00:51:07 Tony via Digitalmars-d-announce wrote:
> On Saturday, 24 March 2018 at 00:12:23 UTC, Jonathan M Davis
>
> wrote:
> > On Friday, March 23, 2018 22:42:34 Tony via
> >
> > Digitalmars-d-announce wrote:
> >> On Friday, 23 March 2018 at 22:32:50 UTC, H. S. Teoh
On Saturday, 24 March 2018 at 00:12:23 UTC, Jonathan M Davis
wrote:
On Friday, March 23, 2018 22:42:34 Tony via
Digitalmars-d-announce wrote:
On Friday, 23 March 2018 at 22:32:50 UTC, H. S. Teoh wrote:
> On Fri, Mar 23, 2018 at 09:45:33PM +, Tony via
>
> Digitalmars-d-announce wrote:
>> On
Github erased me, without any omens / notice, no reply.
So, ShionKeys/, I disappeared on gihub.
On Saturday, 11 November 2017 at 21:02:42 UTC, aberba wrote:
On Friday, 10 November 2017 at 15:06:20 UTC, Shion wrote:
of my project of trying to change the world (ShionKeys),
Yet no one ever change the world.
...Just like Advances in tech doesn't kill poverty, advances in
medicine does
On Friday, March 23, 2018 22:42:34 Tony via Digitalmars-d-announce wrote:
> On Friday, 23 March 2018 at 22:32:50 UTC, H. S. Teoh wrote:
> > On Fri, Mar 23, 2018 at 09:45:33PM +, Tony via
> >
> > Digitalmars-d-announce wrote:
> >> On Friday, 23 March 2018 at 20:43:15 UTC, H. S. Teoh wrote:
> >>
On Friday, 23 March 2018 at 22:32:50 UTC, H. S. Teoh wrote:
On Fri, Mar 23, 2018 at 09:45:33PM +, Tony via
Digitalmars-d-announce wrote:
On Friday, 23 March 2018 at 20:43:15 UTC, H. S. Teoh wrote:
> On Friday, 23 March 2018 at 19:56:03 UTC, Steven
> Schveighoffer wrote:
> > I've worked on
On Fri, Mar 23, 2018 at 09:45:33PM +, Tony via Digitalmars-d-announce wrote:
> On Friday, 23 March 2018 at 20:43:15 UTC, H. S. Teoh wrote:
> >
> > > I've worked on a project where the testing was separated from the
> > > code, and it was a liability IMO. Things would get missed and not
> > >
On Friday, 23 March 2018 at 20:43:15 UTC, H. S. Teoh wrote:
I've worked on a project where the testing was separated from
the code, and it was a liability IMO. Things would get missed
and not tested properly.
That's where Test Driven Development comes in.
Yep. As I mentioned elsewhere,
On Friday, March 23, 2018 13:43:15 H. S. Teoh via Digitalmars-d-announce
wrote:
> Yep. As I mentioned elsewhere, recently I've had to resort to external
> testing for one of my projects, and I'm still working on that right now.
> And already, I'm seeing a liability: rather than quickly locating
On Fri, Mar 23, 2018 at 03:56:03PM -0400, Steven Schveighoffer via
Digitalmars-d-announce wrote:
[..]
> Note that a frequent complaint of std.datetime (at least when it was
> one module) is that the file was too big. While it does hold a lot of
> functionality, the majority of the file size is
On Fri, Mar 23, 2018 at 07:46:34PM +, Johan Engelen via
Digitalmars-d-announce wrote:
> On Thursday, 22 March 2018 at 15:18:40 UTC, Jacob Carlborg wrote:
[...]
> > I completely agree. Although my reason is mostly because there will
> > be too much code in a single file if the regular code and
On 3/23/18 3:46 PM, Johan Engelen wrote:
On Thursday, 22 March 2018 at 15:18:40 UTC, Jacob Carlborg wrote:
On Thursday, 22 March 2018 at 11:00:31 UTC, Atila Neves wrote:
Direct link:
https://atilanevesoncode.wordpress.com/2018/03/22/keep-d-unittests-separated-from-production-code/
I
On Thursday, 22 March 2018 at 15:18:40 UTC, Jacob Carlborg wrote:
On Thursday, 22 March 2018 at 11:00:31 UTC, Atila Neves wrote:
Direct link:
https://atilanevesoncode.wordpress.com/2018/03/22/keep-d-unittests-separated-from-production-code/
I completely agree. Although my reason is mostly
On 3/22/18 6:59 AM, Atila Neves wrote:
Blog post:
https://atilanevesoncode.wordpress.com/
Atila
It's simple. Unittests in imported modules should not be visible. They
should be compiled as if -unittest was not passed.
Even Walter and Andrei are supportive:
On Friday, 23 March 2018 at 00:47:20 UTC, Tony wrote:
I think unittest blocks are good for write-once and
quick-and-dirty projects, or as a first-cut of testing that
ultimately gets moved to a full-grown test suite in a separate
project. I'd prefer not to read source code that has unittest
18 matches
Mail list logo
