Re: Mir Algorithm v0.5.16: @safe ndslice; shortcuts; topology.pairwise instead of isSorted and isStrictlyMonotonic

2017-05-14 Thread 9il via Digitalmars-d-announce
On Sunday, 14 May 2017 at 17:29:44 UTC, jmh530 wrote: On Saturday, 13 May 2017 at 08:10:20 UTC, 9il wrote: https://github.com/libmir/mir-algorithm/releases/tag/v0.5.16 The documentation for mir.functional might need an update based on the refTuple change. The links at the top are missing

Re: Mir Algorithm v0.5.16: @safe ndslice; shortcuts; topology.pairwise instead of isSorted and isStrictlyMonotonic

2017-05-14 Thread jmh530 via Digitalmars-d-announce
On Saturday, 13 May 2017 at 08:10:20 UTC, 9il wrote: https://github.com/libmir/mir-algorithm/releases/tag/v0.5.16 The documentation for mir.functional might need an update based on the refTuple change. The links at the top are missing refTuple and RefTuple. tuple doesn't go anywhere, also

Re: Mir Algorithm v0.5.16: @safe ndslice; shortcuts; topology.pairwise instead of isSorted and isStrictlyMonotonic

2017-05-13 Thread 9il via Digitalmars-d-announce
https://github.com/libmir/mir-algorithm/releases/tag/v0.5.16

Mir Algorithm v0.5.16: @safe ndslice; shortcuts; topology.pairwise instead of isSorted and isStrictlyMonotonic

2017-05-13 Thread 9il via Digitalmars-d-announce
### Slice is safe now User-defined iterators must care about their safety except bounds checks. Bounds are checked in ndslice code. ### Deprecations - `tuple` was renamed to `refTuple` - `isSorted` and `isStrictlyMonotonic` are deprecated. Use `pairwise` and `all` instead. `[float.nan,