On Wednesday, 7 June 2017 at 21:47:58 UTC, John Carter wrote:
> On Monday, 5 June 2017 at 14:23:34 UTC, Mike Parker wrote:
>> https://dlang.org/blog/2017/06/05/compile-time-sort-in-d/
>
> Seems like you have inspired people...
>
> http://blog.zdsmith.com/posts/compiletime-sort-in-nim.html

We should make another post showing the string import feature.

On Wednesday, 7 June 2017 at 20:59:50 UTC, Joakim wrote:
> On Tuesday, 6 June 2017 at 01:08:45 UTC, Mike Parker wrote:
>> On Monday, 5 June 2017 at 17:54:05 UTC, Jon Degenhardt wrote:
>>
>>>
>>> Very nice post!
>>
>> Thanks! If it gets half as many page views as yours did, I'll be happy. Yours is the most-viewed post on the blog -- over 1000 views more than #2 (my GC post), and 5,000 more than #3 (A New Import Idiom).
>
> I was surprised it's so popular, as the proggit thread didn't do that great, but it did well on HN and I now see it inspired more posts for Rust (written by bearophile, I think) and Go, in addition to the Nim post linked here before:
>
> https://users.rust-lang.org/t/faster-command-line-tools-in-d-rust/10992
> https://aadrake.com/posts/2017-05-29-faster-command-line-tools-with-go.html

I was surprised as well, pleasantly of course. Using a simple example may have helped. Personally, I'm not bothered by the specific instances of negative feedback on Reddit. It's hard to write a post that manages to avoid that sort of thing entirely. It was also nice to see related follow-up in the D forums ("how to count lines fast" and "std.csv Performance Review"). It's less if the case for how well suited D's facilities are for the type of problem came across. It's much more clear in the Compile-Time Sort post.

--Jon

On Thursday, June 08, 2017 01:08:42 Jon Degenhardt via Digitalmars-d- announce wrote:
> I was surprised as well, pleasantly of course. Using a simple example may have helped. Personally, I'm not bothered by the specific instances of negative feedback on Reddit. It's hard to write a post that manages to avoid that sort of thing entirely. It was also nice to see related follow-up in the D forums ("how to count lines fast" and "std.csv Performance Review"). It's less if the case for how well suited D's facilities are for the type of problem came across. It's much more clear in the Compile-Time Sort post.

And even the reddit discussion on the compile-time sort post devolved a bit into arguments over stuff like enums as manifest constants. Using reddit to get information out there is useful, but from what I've seen, the comments usually devolve into a fairly negative discussion. I don't spend much time on reddit though.

- Jonathan M Davis

On Tuesday, 6 June 2017 at 01:08:45 UTC, Mike Parker wrote:
> On Monday, 5 June 2017 at 17:54:05 UTC, Jon Degenhardt wrote:
>
>>
>> Very nice post!
>
> Thanks! If it gets half as many page views as yours did, I'll be happy. Yours is the most-viewed post on the blog -- over 1000 views more than #2 (my GC post), and 5,000 more than #3 (A New Import Idiom).

Seems like this crowd-editing stuff really works!

On Wednesday, 7 June 2017 at 21:47:58 UTC, John Carter wrote:
> On Monday, 5 June 2017 at 14:23:34 UTC, Mike Parker wrote:
>> https://dlang.org/blog/2017/06/05/compile-time-sort-in-d/
>
> Seems like you have inspired people...
>
> http://blog.zdsmith.com/posts/compiletime-sort-in-nim.html

Seeing that the one and only D example in the nim article is a broken one (using static instead of enum or static immutable for 'b') we should have started with a correct example before showing the broken one... Good to know for next time.

On 06/08/2017 09:07 PM, cym13 wrote:
> Seeing that the one and only D example in the nim article is a broken one (using static instead of enum or static immutable for 'b') we should have started with a correct example before showing the broken one... Good to know for next time.

Broken? It works just fine.

On Thursday, 8 June 2017 at 19:07:50 UTC, cym13 wrote:

>
> Seeing that the one and only D example in the nim article is a broken one (using static instead of enum or static immutable for 'b') we should have started with a correct example before showing the broken one... Good to know for next time.

static variables are initialized with compile-time values. They don't need be immutable for that.

On Friday, 9 June 2017 at 01:34:14 UTC, Mike Parker wrote:
> On Thursday, 8 June 2017 at 19:07:50 UTC, cym13 wrote:
>
>>
>> Seeing that the one and only D example in the nim article is a broken one (using static instead of enum or static immutable for 'b') we should have started with a correct example before showing the broken one... Good to know for next time.
>
> static variables are initialized with compile-time values. They don't need be immutable for that.

they need immutable if you want to use them again at compile-time.
Therefore it is a good habit to get into.

On Friday, 9 June 2017 at 01:34:14 UTC, Mike Parker wrote:
> On Thursday, 8 June 2017 at 19:07:50 UTC, cym13 wrote:
>
>>
>> Seeing that the one and only D example in the nim article is a broken one (using static instead of enum or static immutable for 'b') we should have started with a correct example before showing the broken one... Good to know for next time.
>
> static variables are initialized with compile-time values. They don't need be immutable for that.

My bad, I miscopied the code.

On 6/7/17 5:47 PM, John Carter wrote:
> On Monday, 5 June 2017 at 14:23:34 UTC, Mike Parker wrote:
>> https://dlang.org/blog/2017/06/05/compile-time-sort-in-d/
>
> Seems like you have inspired people...
>
> http://blog.zdsmith.com/posts/compiletime-sort-in-nim.html
>
>

That is kind of neat. While I can say that D can perform technically the same feat via pragma(msg, ...) and importing a file directly (would leave a comment on the blog, but there isn't a spot for it), the fact that you can execute arbitrary code in a block at compile time that can use the *actual* i/o routines you would use at runtime is pretty impressive.

Stefan would have a field day with this power :)

-Steve