Comments on: The Pi Day Challenge for the Most Expressive Code – Results

By: Dimitar Mirchev

Dimitar Mirchev — Fri, 17 Mar 2017 13:24:00 +0000

In reply to Porsche9II. There is special verion that works with VS2017. I used the new Visual Studio Open Folder/CMAKE to compile and experiment with one of the examples.

By: Mikulas Florek

Mikulas Florek — Tue, 14 Mar 2017 13:41:00 +0000

In reply to triangle_soup {neil}. I am not familiar with ranges at all and the only reason I can understand the code is only because the variables are properly named and I had to deduct a lot. What's also bad is that I tried to educate myself on the ranges but googling "ranges::view::take" returns nothing useful.

By: Will K

Will K — Tue, 14 Mar 2017 13:36:00 +0000

In reply to triangle_soup {neil}.

> neither familiar with the original problem

He clearly described the problem, including all formulae necessary.

> nor the Ranges library

I never used Ranges before this. It’s even in my comment header for the code

> The use of capitalisation for const variables MAKES the CODE hard TO read.

Sorry, that’s just my style. I’m not sure of a reasonable alternative either. PascalCase is for classes, camelCase is for local variables and methods. I like being able to see whether or not something is const just by looking at it, and I refuse to adopt hungarian notation (Google uses a k prefix).

By: triangle_soup {neil}

triangle_soup {neil} — Tue, 14 Mar 2017 12:27:00 +0000

I think an interesting experiment would be to give that code to a group of programmers who are neither familiar with the original problem nor the Ranges library (I’m guessing the majority of C++ programmers) and to see if they can tell you what problem it is solving. If it’s truly expressive then they should be able to tell you very quickly.

The use of capitalisation for const variables MAKES the CODE hard TO read. I really wish people would stop that, especially given that we try and ‘const’ everything these days.

Nice solution, though.

By: Porsche9II

Porsche9II — Tue, 14 Mar 2017 10:44:00 +0000

Bonus points for “std::nexttoward(radius, 2 * radius)” for generating random numbers in [-r, r] and the static declaration of the rng for avoiding the birthday problem (for parallelization and smaller code size use http://www.pcg-random.org/ with auto_seeder)

expressive code equals #include

Is Ranges working with the new VS2017 C++ compiler – anyone tested?