Jacek Sieka 638e7acc8e
deprecate ranges (#31)
Without lifetime tracking, ranges pose a number of issues with regards
to memory safety - use openArray instead which is limited but safe.

In its present form, ranges take a copy of whatever is passed to them
which obscures the copies that they take, leading to misleading and slow
code.

If openArray is not applicable, simply do a seq copy - it's fine and
really doesn't matter in 95% of all cases, then profile and use other
techniques where needed.
2020-05-07 07:11:43 +02:00
..
2020-05-07 07:11:43 +02:00
2019-12-13 15:31:19 +02:00
2019-12-13 15:31:19 +02:00
2019-12-13 15:31:19 +02:00
2020-04-10 22:40:00 +03:00
2020-01-29 02:42:50 +02:00
2019-07-06 19:12:24 +02:00
2020-04-10 22:40:00 +03:00
2019-10-23 09:36:16 +09:00
2020-04-22 16:39:37 +03:00
2020-05-07 07:11:43 +02:00
2019-07-06 19:12:24 +02:00
2020-04-07 11:43:07 +02:00
2020-04-23 06:46:10 +02:00
2019-07-06 19:12:24 +02:00

Candidates for standard library inclusion - functions and helpers that are too small to put in their own git repository