Re: Why I Like D

2022-01-11 Thread forkit via Digitalmars-d-announce
On Wednesday, 12 January 2022 at 02:37:47 UTC, Walter Bright wrote: "Why I like D" is on the front page of HackerNews at the moment at number 11. https://news.ycombinator.com/news surely this article needs to be balanced, with another article, titled 'why I don't like D' ;-) (..but written

Why I Like D

2022-01-11 Thread Walter Bright via Digitalmars-d-announce
"Why I like D" is on the front page of HackerNews at the moment at number 11. https://news.ycombinator.com/news

Re: Why I Like D

2022-01-11 Thread ag0aep6g via Digitalmars-d-announce
On 12.01.22 03:37, Walter Bright wrote: "Why I like D" is on the front page of HackerNews at the moment at number 11. https://news.ycombinator.com/news https://news.ycombinator.com/item?id=29863557 https://aradaelli.com/blog/why-i-like-d/

Re: Why I Like D

2022-01-11 Thread forkit via Digitalmars-d-announce
On Wednesday, 12 January 2022 at 06:27:47 UTC, forkit wrote: surely this article needs to be balanced, with another article, titled 'why I don't like D' ;-) (..but written by someone who really knows D). oh. btw. I'd love to see Walter (or Andrei, or both) write this article ;-)

Re: Why I Like D

2022-01-11 Thread surlymoor via Digitalmars-d-announce
On Wednesday, 12 January 2022 at 02:37:47 UTC, Walter Bright wrote: "Why I like D" is on the front page of HackerNews at the moment at number 11. https://news.ycombinator.com/news Nice article, especially this paragraph: In case you are writing a performance critical piece of software,

Re: fixedstring: a @safe, @nogc string type

2022-01-11 Thread WebFreak001 via Digitalmars-d-announce
On Tuesday, 11 January 2022 at 11:16:13 UTC, Moth wrote: On Tuesday, 11 January 2022 at 03:20:22 UTC, Salih Dincer wrote: [snip] glad to hear you're finding it useful! =] hm, i'm not sure how i would go about fixing that double character issue. i know there's currently some wierdness with

Re: fixedstring: a @safe, @nogc string type

2022-01-11 Thread H. S. Teoh via Digitalmars-d-announce
On Tue, Jan 11, 2022 at 11:16:13AM +, Moth via Digitalmars-d-announce wrote: > On Tuesday, 11 January 2022 at 03:20:22 UTC, Salih Dincer wrote: > > [snip] > > glad to hear you're finding it useful! =] One minor usability issue I found just glancing over the code: many of your methods take

Re: fixedstring: a @safe, @nogc string type

2022-01-11 Thread Moth via Digitalmars-d-announce
On Tuesday, 11 January 2022 at 03:20:22 UTC, Salih Dincer wrote: [snip] glad to hear you're finding it useful! =] hm, i'm not sure how i would go about fixing that double character issue. i know there's currently some wierdness with wchars / dchars equality that needs to be fixed [shouldn't

Re: fixedstring: a @safe, @nogc string type

2022-01-11 Thread vit via Digitalmars-d-announce
On Tuesday, 11 January 2022 at 11:16:13 UTC, Moth wrote: On Tuesday, 11 January 2022 at 03:20:22 UTC, Salih Dincer wrote: [snip] glad to hear you're finding it useful! =] ... i know there's currently some wierdness with wchars / dchars equality that needs to be fixed [shouldn't be too much

Re: fixedstring: a @safe, @nogc string type

2022-01-11 Thread Paul Backus via Digitalmars-d-announce
On Tuesday, 11 January 2022 at 17:55:28 UTC, H. S. Teoh wrote: Generally, I'd advise not conflating your containers with ranges over your containers: I'd make .opSlice return a traditional D slice (i.e., const(char)[]) instead of a FixedString, and just require writing `[]` when you need to

Re: Error message formatter for range primitives

2022-01-11 Thread WebFreak001 via Digitalmars-d-announce
On Wednesday, 5 January 2022 at 09:32:36 UTC, Robert Schadek wrote: In https://forum.dlang.org/post/tfdycnibnxyryizec...@forum.dlang.org I complained that error message related to range primitives like isInputRange, especially on template constraints, are not great. [...] cool! As I'm not