Voting For std.experimental.ndslice

[Ilya Yaroshenko via Digitalmars-d]

On Tuesday, 29 December 2015 at 13:30:47 UTC, Márcio Martins 
wrote:
> On Tuesday, 29 December 2015 at 07:45:14 UTC, Ilya Yaroshenko 
> wrote:
>> On Monday, 28 December 2015 at 22:39:45 UTC, Ilya Yaroshenko 
>> wrote:
>>> On Monday, 28 December 2015 at 21:43:35 UTC, Robert burner 
>>> Schadek wrote:
>>>> [...]
>>>
>>> Agreed
>>>
>>> 1. First paragraph was replaced by your variant.
>>> 2. Binary representation was moved to Slice type 
>>> documentation.
>>> 3. Small "Quick Start" was added, so new user will start from 
>>> `sliced` and `Slice`.
>>>
>>> http://dtest.thecybershadow.net/artifact/website-76234ca0eab431527327d5ce1ec0ad74c6421533-081dd6e9e8b3810a143d0a5fcba8d60b/web/phobos-prerelease/std_experimental_ndslice.html
>>>
>>> Thanks!
>>>
>>> Ilya
>>
>> Fix English: 
>> http://dtest.thecybershadow.net/artifact/website-76234ca0eab431527327d5ce1ec0ad74c6421533-bfed2500425eb407bf2c97fc72e8a0c5/web/phobos-prerelease/std_experimental_ndslice.html
>
> If I am reading the code right, the number of dimensions must 
> always be known at compile time, right? Is so, I suppose it was 
> a performance-oriented decision and not an oversight, correct?

This package is performance oriented. In the same time it is more 
flexible comparing with numpy.

Simple optimisation check:
Source: https://gist.github.com/9il/bc7966823d96557c566c
LDC disassembled: 
https://gist.github.com/9il/47aea1621a9fba609869 (all functions 
are inlined)