On Thursday, 28 July 2016 at 15:48:58 UTC, Seb wrote:
We call them DIP (D Improvement Proposals) and I think it's a
lot more productive way to discuss improvements than in the
forum.
Eh. I hoped that somewhere in that explosion of discussion on the
topic the problem had been solved and I had
Don't you just hate it when you google a problem and find a post
from yourself asking the same question?
In 2013 I ran into the UTF8 invalid char autodecode UTFException,
and the answer then was "use std.encoding.sanitize" and my
opinion looking at the implementation, was then, as is now... Ew
On Tuesday, 8 December 2015 at 00:40:29 UTC, tsbockman wrote:
Someone still needs to review the PR, though.
Thanks! Looks like it's been merged already.
It was a double problem... I failed to read the bit about
advancing the ref and then the old big @@@BUG@@@ comment in the
unit test made m
So whilst attempt to convert from a hex string (without the 0x)
to int I bumped into the @@@BUG@@@ the size of China
https://github.com/D-Programming-Language/phobos/blob/master/std/conv.d#L2270
Is there a bugzilla issue number tracking this?
Searching for conv and parse in the issue trac
On Wednesday, 2 September 2015 at 21:43:17 UTC, ponce wrote:
Additionally, I was said weeks ago on this NG that and signed
overflow in D is not actually Undefined Behaviour.
Interesting.. The reference is fairly terse on exactly what
happens, is it more formally specified anywhere? In which c
On Wednesday, 2 September 2015 at 11:03:00 UTC, ponce wrote:
On Tuesday, 1 September 2015 at 23:06:50 UTC, John Carter wrote:
C/C++ discussion here
http://blog.robertelder.org/signed-or-unsigned-part-2/
D rules here...
http://dlang.org/type.html#integer-promotions
Everything Bjarn
C/C++ discussion here
http://blog.robertelder.org/signed-or-unsigned-part-2/
D rules here...
http://dlang.org/type.html#integer-promotions
On Monday, 10 February 2014 at 22:19:19 UTC, bearophile wrote:
http://dpaste.dzfl.pl/821527e71343
Your paste has expired / no longer there but the subject has
come up again...
http://www.wilfred.me.uk/blog/2014/10/20/the-fastest-bigint-in-the-west/
https://lobste.rs/s/sfie8j/the_fastes
So in Ruby and R and Scheme and... I have happily used map /
collect for years and years.
Lovely thing.
So I did the dumb obvious of
string[] stringList = map!...;
And D barfed, wrong type, some evil voldemort thing again.
So..
auto stringList = map!;
and we're good..
and happil
Ali, of course, is right. The only thing I'd add is for a
Windowsy programmer (unless you have cygwin installed) you
probably want something like "cmd.exe" instead of bash.
On Monday, 23 June 2014 at 21:49:29 UTC, Ary Borenszweig wrote:
Union types are very common (I use them every day), and IMHO
it's very nice to have them included in the language (either
built-in or as a library solution). As a library solution I
would do something like this:
Union!(int, stri
On Monday, 23 June 2014 at 21:26:19 UTC, Chris Williams wrote:
More likely what you want are variants:
Hmm. Interesting.
Yes, Variant and VariantArray are much closer to the dynamic
language semantics...
But the interesting thing is Tuple is much closer to "What I
Mean" when I create thes
I guess between perl and Ruby and Scheme etc. I got used to
creating hybrid containers
Want a pair of [string, fileList]? Just make an Array with two
items, one a string, one and array of strings. Done.
D barfed... leaving me momentarily stunned... then Oh Yes, type
safety, Tuple's are t
13 matches
Mail list logo
