On Saturday, 6 May 2017 at 22:16:34 UTC, سليمان السهمي (Soulaïman
Sahmi) wrote:
Recordings hidden/removed? do we need to wait another month to
get them?
Supposedly just until Monday. I really don't get why they
couldn't leave the full recordings up while they're in the
process of slicing
On Saturday, 29 October 2016 at 11:25:17 UTC, Nicholas Wilson
wrote:
On Saturday, 29 October 2016 at 10:21:02 UTC, Guillaume Piolat
wrote:
On Saturday, 29 October 2016 at 01:43:03 UTC, Nicholas Wilson
wrote:
If you have any experience with either OpenCL or CUDA we'd
love to have your input.
First of all, awesome work. It's great to see that it's possible
to match or even exceed the performance of hand-crafted assembly
implementations with generic code.
I would suggest adding more information on how the Eigen results
were obtained. Unlike OpenBLAS, Eigen performance does often
On Friday, 9 September 2016 at 13:32:16 UTC, Russel Winder wrote:
Why write algorithms in C or C++ when you can do it in Chapel?
For the moment, the objective answers to that question seem: you
need GPGPU (especially CUDA, which is vastly more convenient to
use from C++ than from anything
On Thursday, 8 September 2016 at 10:20:42 UTC, Russel Winder
wrote:
On Wed, 2016-09-07 at 20:29 +, deXtoRious via
Digitalmars-d-learn wrote:
[…]
More to the general point of the discussion, I find that most
scientifically minded users of Python already appreciate some
of the inherent
On Wednesday, 7 September 2016 at 20:57:03 UTC, data pulverizer
wrote:
On Wednesday, 7 September 2016 at 20:29:51 UTC, deXtoRious
wrote:
On Wednesday, 7 September 2016 at 19:19:23 UTC, data
pulverizer wrote:
The "One language to rule them all" motif of Julia has hit
the rocks; one reason is
On Wednesday, 7 September 2016 at 19:19:23 UTC, data pulverizer
wrote:
The "One language to rule them all" motif of Julia has hit the
rocks; one reason is because they now realize that their
language is being held back because the compiler cannot infer
certain types for example:
On Wednesday, 24 February 2016 at 03:33:14 UTC, Mike Parker wrote:
On Tuesday, 23 February 2016 at 20:03:30 UTC, dextorious wrote:
For instance, I am still not sure how to make it pass the -O5
switch to the LDC2 compiler and the impression I got from the
documentation is that explicit manual
On Tuesday, 23 February 2016 at 14:07:22 UTC, Marc Schütz wrote:
On Tuesday, 23 February 2016 at 11:10:40 UTC, ixid wrote:
We really need to standard algorithms to be fast and perhaps
have separate ones for perfect technical accuracy.
While I agree with most of what you're saying, I don't
On Tuesday, 23 February 2016 at 11:10:40 UTC, ixid wrote:
On Monday, 22 February 2016 at 15:43:23 UTC, dextorious wrote:
I do have to wonder, however, about the default settings of
dub in this case. Having gone through its documentation, I
might still not have guessed to try the compiler
On Sunday, 21 February 2016 at 16:20:30 UTC, bachmeier wrote:
First, a minor point, the D community is usually pretty careful
not to frown on a particular coding style (unlike some
communities) so if you are comfortable writing loops and it
gives you the fastest code, you should do so.
On
First of all, I am pleasantly surprised by the rapid influx of
helpful responses. The community here seems quite wonderful. In
the interests of not cluttering the thread too much, since the
advice given here has many commonalities, I will only try to
respond once to each type of suggestion.
I've been vaguely aware of D for many years, but the recent
addition of std.experimental.ndslice finally inspired me to give
it a try, since my main expertise lies in the domain of
scientific computing and I primarily use Python/Julia/C++, where
multidimensional arrays can be handled with a
13 matches
Mail list logo
