Files
weave-scope/report
Matthias Radestock 3de04685f8 optimisation: pre-allocate, and fewer slices during summarisation
Pre-allocating slices really pays dividends when we create loads of
them and they don't grow very large.

We take special care to return nil rather than 0-length slices. This
a) saves further on allocation, and b) is required for some crude
tests to pass that match on nil rather than length.

Also, a bunch of code in templates/tables used slices as Maybe's,
i.e. returning nil or a single-element slice, which is horrendously
inefficient. Eliminating these saves a lot of allocations.
2017-12-25 12:33:43 +00:00
..
2017-07-04 07:35:30 +01:00
2017-07-04 07:35:30 +01:00
2017-07-04 07:35:30 +01:00
2017-11-29 21:56:55 +00:00
2016-12-07 11:22:40 +00:00
2017-07-04 07:35:30 +01:00
2016-12-07 11:22:40 +00:00
2017-12-24 22:30:20 +00:00
2017-12-24 22:30:20 +00:00
2017-07-04 07:35:30 +01:00