On Wednesday, 18 May 2016 at 18:02:12 UTC, Bruno Medeiros wrote:
While DDT technically work oks with GDB (the GDB from mingw-w64
that is), you are right, there isn't a compiler on Windows that
supplies debug info in the way GDB understands. See
https://wiki.dlang.org/Debuggers.
DMD produces d
On Monday, 16 May 2016 at 13:46:11 UTC, Andrei Alexandrescu wrote:
Uses D for examples, showcases Design by Introspection, and
rediscovers a fast partition routine. It was quite well
received. https://www.youtube.com/watch?v=AxnotgLql0k
Andrei
Nice presentation.
The code applying the sentin
On Wednesday, 18 May 2016 at 20:10:09 UTC, Jonathan M Davis wrote:
So, while we do have enforcement of how ranges _can_ be used,
we don't have enforcement of how they _are_ used, and I don't
expect that we'll ever get that.
It would help if there was documented standard testing procedure
(and
On 5/16/16 9:46 AM, Andrei Alexandrescu wrote:
Uses D for examples, showcases Design by Introspection, and rediscovers
a fast partition routine. It was quite well received.
https://www.youtube.com/watch?v=AxnotgLql0k
This talk took a big gambit and it seems to have worked well. Per
https://www
On 5/19/16 4:12 AM, Jens Müller wrote:
The code applying the sentinel optimization assumes mutability of
the input. That needs to be checked for.
Indeed. As I mentioned after discussing find, I didn't worry about those
checks assuming they were obvious.
That's fine for partition
because tha
On 5/18/16 7:42 AM, Manu via Digitalmars-d-announce wrote:
On 16 May 2016 at 23:46, Andrei Alexandrescu via
Digitalmars-d-announce wrote:
Uses D for examples, showcases Design by Introspection, and rediscovers a
fast partition routine. It was quite well received.
https://www.youtube.com/watch?v
On Wednesday, May 18, 2016 22:23:45 jmh530 via Digitalmars-d-announce wrote:
> On Wednesday, 18 May 2016 at 20:10:09 UTC, Jonathan M Davis wrote:
> > At this point, if anyone ever calls front with parens, they're
> > doing it wrong.
>
> Is this true of all @property functions? Should this be noted
On Thursday, May 19, 2016 09:05:53 Kagamin via Digitalmars-d-announce wrote:
> On Wednesday, 18 May 2016 at 20:10:09 UTC, Jonathan M Davis wrote:
> > So, while we do have enforcement of how ranges _can_ be used,
> > we don't have enforcement of how they _are_ used, and I don't
> > expect that we'll
On 19/05/2016 3:50 AM, Stefan Koch wrote:
I am currently designing an IR to feed into the CTFE Evaluator.
I am aware that this could potentially make it harder to get things
merged since DMD already has the glue-layer.
It's always more difficult to justify merging more complexity. But if
you
On Thursday, 19 May 2016 at 12:04:31 UTC, Andrei Alexandrescu
wrote:
On 5/19/16 4:12 AM, Jens Müller wrote:
What test data did you use?
An instance for benchmarking is generated as follows. Given nnz
which is the sum of non-zero indices in input vector a and b.
auto lengthA = uniform!"[]"
On Thursday, 19 May 2016 at 12:10:36 UTC, Jonathan M Davis wrote:
[snip]
Very informative, as always.
I had not realized the implication of front being called without
parens, such as front being something that isn't an @property
function (esp. variable). Are there any ranges in phobos (you
On 5/17/16 8:36 PM, H. S. Teoh via Digitalmars-d-announce wrote:
On Tue, May 17, 2016 at 08:19:48PM +, Vladimir Panteleev via
Digitalmars-d-announce wrote:
On Tuesday, 17 May 2016 at 17:26:59 UTC, Steven Schveighoffer wrote:
However, it's perfectly legal for a front function not to be tagg
On 19/05/2016 08:41, Vadim Lopatin wrote:
On Wednesday, 18 May 2016 at 18:02:12 UTC, Bruno Medeiros wrote:
While DDT technically work oks with GDB (the GDB from mingw-w64 that
is), you are right, there isn't a compiler on Windows that supplies
debug info in the way GDB understands. See
https://w
On Thu, May 19, 2016 at 09:21:40AM -0400, Steven Schveighoffer via
Digitalmars-d-announce wrote:
> On 5/17/16 8:36 PM, H. S. Teoh via Digitalmars-d-announce wrote:
> > On Tue, May 17, 2016 at 08:19:48PM +, Vladimir Panteleev via
> > Digitalmars-d-announce wrote:
> > > On Tuesday, 17 May 2016
On Tuesday, 17 May 2016 at 14:06:37 UTC, Jack Stouffer wrote:
http://jackstouffer.com/blog/d_auto_decoding_and_you.html
Based on the recent thread in General, I wrote this blog post
that's designed to be part beginner tutorial, part objective
record of the debate over it, and finally my opinio
On Thursday, 19 May 2016 at 17:16:54 UTC, Taylor Hillegeist wrote:
If people want auto coding behavior shouldn't they just use or
convert to dchar?
No, they need to _decode_ to dchar. I don't know if you
miss-typed, but if you didn't, this is exactly what I was talking
about in the article:
On Thursday, 19 May 2016 at 12:04:31 UTC, Andrei Alexandrescu
wrote:
On 5/19/16 4:12 AM, Jens Müller wrote:
---
if (a.length == 0 || b.length == 0)
return 0;
const amax = a.length - 1, bmax = b.length - 1;
size_t i,j = 0;
double sum = 0;
for (;;)
{
if (a[i].index < b[j].index) {
On 05/19/2016 05:36 PM, Jens Müller wrote:
I'm not seeing it. Let me explain.
Consider the input a = [1] and b = [2, 3] (I only write the indices).
The smallest back index is 1, i.e., a.back is the chosen sentinel.
Nonono, you stamp the largest index over the smaller index. So you
overwrite a
On 05/19/2016 05:36 PM, Jens Müller wrote:
I removed the code to optimize for large gaps. Because it is only
confusing. I may generate some benchmark data with larger gaps later to
see whether it is worthwhile for such data.
For skipping large gaps quickly, check galloping search (google for it
On Tuesday, 17 May 2016 at 14:06:37 UTC, Jack Stouffer wrote:
http://jackstouffer.com/blog/d_auto_decoding_and_you.html
There are lots of places where invalid Unicode is either
commonplace or legal, e.g. Linux file names, and therefore
auto decoding cannot be used. It turns out in the wild th
On Thursday, 19 May 2016 at 22:02:53 UTC, Andrei Alexandrescu
wrote:
On 05/19/2016 05:36 PM, Jens Müller wrote:
I'm not seeing it. Let me explain.
Consider the input a = [1] and b = [2, 3] (I only write the
indices).
The smallest back index is 1, i.e., a.back is the chosen
sentinel.
Nonono,
On Thursday, 19 May 2016 at 22:04:56 UTC, Andrei Alexandrescu
wrote:
On 05/19/2016 05:36 PM, Jens Müller wrote:
I removed the code to optimize for large gaps. Because it is
only
confusing. I may generate some benchmark data with larger gaps
later to
see whether it is worthwhile for such data.
Unfortunately in this particular case, CDT's debugging is pretty
fancy and is going to need most if not all of the MI.
On Thursday, 19 May 2016 at 13:29:14 UTC, Bruno Medeiros wrote:
On 19/05/2016 08:41, Vadim Lopatin wrote:
On Wednesday, 18 May 2016 at 18:02:12 UTC, Bruno Medeiros
wrote:
Whil
On Friday, 20 May 2016 at 03:15:46 UTC, E.S. Quinn wrote:
Unfortunately in this particular case, CDT's debugging is
pretty fancy and is going to need most if not all of the MI.
I also don't know which MI commands need to be supported to
have it work with DDT. The thing is I didn't write the GD
On 19 May 2016 at 22:10, Andrei Alexandrescu via
Digitalmars-d-announce wrote:
> On 5/18/16 7:42 AM, Manu via Digitalmars-d-announce wrote:
>>
>> On 16 May 2016 at 23:46, Andrei Alexandrescu via
>> Digitalmars-d-announce wrote:
>>>
>>> Uses D for examples, showcases Design by Introspection, and r
25 matches
Mail list logo