On Saturday, October 12, 2019 9:48:02 PM MDT jmh530 via Digitalmars-d-learn
wrote:
> On Saturday, 12 October 2019 at 21:44:57 UTC, Jonathan M Davis
>
> wrote:
> > [snip]
>
> Thanks for the reply.
>
> As with most people, I don't write a lot of D code that uses
> classes that much.
>
> The use
On Saturday, 12 October 2019 at 21:44:57 UTC, Jonathan M Davis
wrote:
[snip]
Thanks for the reply.
As with most people, I don't write a lot of D code that uses
classes that much.
The use case I'm thinking of is with allocators, which - to be
honest - is not something I deal with much in
On Saturday, October 12, 2019 2:11:28 PM MDT jmh530 via Digitalmars-d-learn
wrote:
> On Friday, 11 October 2019 at 17:50:42 UTC, Jonathan M Davis
>
> wrote:
> > [snip]
>
> A very thorough explanation!
>
> One follow-up question: would it be possible to mimic the
> behavior of Java generics in D?
On Saturday, 12 October 2019 at 16:34:01 UTC, Carsten Schlote
wrote:
Nice work, Ron!
Thanks, Carsten.
I'm just converted some of you examples into dub based
projects, and compiled and run them a normal intel PC and a
Raspberry. As a prerequisite I had to install the following on
a
On Friday, 11 October 2019 at 17:50:42 UTC, Jonathan M Davis
wrote:
[snip]
A very thorough explanation!
One follow-up question: would it be possible to mimic the
behavior of Java generics in D?
On Saturday, 12 October 2019 at 13:50:46 UTC, IGotD- wrote:
On Saturday, 12 October 2019 at 09:52:59 UTC, Jonathan M Davis
wrote:
[...]
This would be helpful. About all C++ unit test frameworks have
named test and you can select a specific one or several in the
command line. Very useful
On Tuesday, 8 October 2019 at 10:00:00 UTC, Ron Tarrant wrote:
Today starts a new series on the Notebook widget. Over the next
few weeks, we'll dig in deep, looking at single-tab and
multiple-tab demos, customizing the look of the actual tabs,
adding and removing tabs... a whole ton of stuff.
On Saturday, 12 October 2019 at 09:52:59 UTC, Jonathan M Davis
wrote:
On Saturday, October 12, 2019 2:18:02 AM MDT Martin Brezeln via
Digitalmars- d-learn wrote:
Is it possible to execute only certain modules or tests which
are defined in certain directories?
For example, in go one can run
On Saturday, 12 October 2019 at 11:37:12 UTC, Andre Pany wrote:
- With next Dub version, d-scanner is integrated. Just call dub
lint within your dub project folder. This also makes the CI use
case much greater.
Sound like the best solution. Using dub seems to be the best way
for build D
On Saturday, 12 October 2019 at 04:55:02 UTC, Carsten Schlote
wrote:
Hi,
many companies started to use CI pipelines, and as part of
their pipelines they introduced mandatory linting for source
code.
There are tools for many languages, esp. for C/C++. These tools
usually return '0' on
On Saturday, 12 October 2019 at 09:52:59 UTC, Jonathan M Davis
wrote:
You could set up your build so that you had targets which only
compiled specific directories so that the only unit tests that
were run were the ones in those directories, but I don't think
that it's possible to do anything
On Saturday, October 12, 2019 2:18:02 AM MDT Martin Brezeln via Digitalmars-
d-learn wrote:
> Is it possible to execute only certain modules or tests which are
> defined in certain directories?
>
> For example, in go one can run "go test ./XYZ" to execute ony
> tests in ./XYZ or "go test ./..." to
hello reader
The days of technology and our lives gradually change with the
pace of development, and we work from morning till night to never
take a rest to catch up with life. It is not uncommon because we
need to work to build a better life. It is so tiring that it
keeps repeating every day
Is it possible to execute only certain modules or tests which are
defined in certain directories?
For example, in go one can run "go test ./XYZ" to execute ony
tests in ./XYZ or "go test ./..." to execute all the tests in and
under the current directory.
Please don't get me wrong, i do not
14 matches
Mail list logo
