• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

frioux / Syntax-Keyword-Junction / 25 / 4
100%
master: 100%

Build:
DEFAULT BRANCH: master
Ran 14 Dec 2018 03:31PM UTC
Files 18
Run time 1s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

14 Dec 2018 03:30PM UTC coverage: 100.0%. Remained the same
25.4

push

travis-ci

frioux
Remove ambiguity in input/limits comparison example

As mentioned in GitHub issue #10, the input/limits comparison example in
the documentation is ambiguous; it could be interpreted as "compare each
element of `@input` with each element of `@limits` and return the `all`
junction of the comparisons".  However this isn't the case, for instance:

```
use strict;
use warnings;

use Syntax::Keyword::Junction qw( all );

my @input = (1, 2, 3, 4, 5, 6);
my @limits = (4, 4, 4, 4, 4, 4);

if (all(@input) <= scalar @limits) {
    print "all input less than or equal to limits\n";
}
else {
    print "not all input less than or equal to limits\n";
}
```

prints "all input less than or equal to limits", but the last two
elements of the `@input` array are greater than the limits.  However,
the input elements are all less than or equal to the length of the
`@limits` array.  If one reduces the length of the `@limits` array, then
the code above prints "not all input less than or equal to limits".
This is the same behaviour as in Perl6 (from the REPL):

```
> all(1, 2, 3, 4, 5, 6) <= (4, 4, 4, 4, 4, 4)
all(True, True, True, True, True, True)
> all(1, 2, 3, 4, 5, 6) <= (4, 4, 4, 4, 4)
all(True, True, True, True, True, False)
```

Consequently, adding the `scalar` keyword in the example makes this
behaviour more obvious.

838 of 838 relevant lines covered (100.0%)

5.19 hits per line

Source Files on job 25.4
  • Tree
  • List 0
  • Changed 3
  • Source Changed 2
  • Coverage Changed 2
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Build 23
  • Travis Job 25.4
  • 35a16bc3 on github
  • Prev Job for on master (#22.5)
  • Next Job for on master (#27.2)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc