3
4%
master: 4%

Ran 09 Jul 2019 03:30PM UTC

Files 676

Run time 2min

Badge

Embed ▾

Committed 09 Jul 2019 02:53PM UTC coverage: 76.424% (+0.003%) from 76.421%

Job # TEST_SUITES="docomp testtravis" ABI=64 HPCGAP=yes

Build Type

push

travis-ci

Committed by

ChrisJefferson

Commit Message

Add PositionSortedBy

One thing to point out is that the interface is a bit different from
PositionSorted, which might be confusing: the object you pass in is
*not* a (potential) element of the list, but rather the result of
applying the "by func" to an object (or at least something that looks
like such a result). The reason: first off, replacing the element by its
func value would be the very first thing done by any implementation
anyway. And a typical application of this function is to search for an
object matching a a certain criterion -- say, the first item which is a
list whose first entry is 42. With the current model, one can write

    PositionSortedBy([ "a", "ab" ], 4, Length);

and is not forced to first construct an actual object, like here:

    PositionSortedBy([ "a", "ab" ], "abcd", Length);

In this example, that's a pretty small saving, but in bigger examples,
it can add up. In particular, this is motivated by real world usage
of this function.

Run Details

245229 of 320879 relevant lines covered (76.42%)

8089589.84 hits per line

gap-system / gap / 10202 / 3
4%
master: 4%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 10202.3 (TEST_SUITES="docomp testtravis" ABI=64 HPCGAP=yes)

gap-system / gap / 10202 / 3 4% master: 4%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 10202.3 (TEST_SUITES="docomp testtravis" ABI=64 HPCGAP=yes)

gap-system / gap / 10202 / 3
4%
master: 4%

README BADGES
x