1
71%
master: 63%

Ran 10 May 2019 07:28PM UTC

Files 7

Run time 2s

Badge

Embed ▾

Committed 10 May 2019 07:25PM UTC coverage: 69.705% (-1.3%) from 70.986%

Job # CONTEXT=abs

Build Type

Pull #219

travis-ci-com

Committed by

web-flow

Commit Message

Implicit return values (`null`), closes #217

This PR makes it possible to skip specifying a
return value, a common scenario when we want to exit,
for example, an IF statement:

```
if something {
  return;
}
```

Note that a value-less return statement needs to end with
a semicolon, else we would need substantial changes to our
lexer in order to carry forward new line breaks. Currently,
line breaks are not passed onto the parser, so the parser
wouldn't know whether to trigger a default return value
based on a line break:

```
if something {
  return # the parser would try to go ahead and parse the '{' as a return value
}
```

This also means there's a tricky behavior (documented in the docs),
as if the user forgets to include a semicolon and the next line contains
a valid expression, the expression will be used as return value:

```
if something {
  return
  1
} # the return value is 1
```

All considered, I think these trade-offs are ok, and rather than
undergoing an extensive refactoring of lexer/parser I would throw
this feature out there and then figure out if the community is too
annoyed by these couple of quirks...

Pull Request Pull Request #219: Implicit return values (`null`), closes #217

Run Details

2455 of 3522 relevant lines covered (69.7%)

38.26 hits per line

abs-lang / abs / 527 / 1
71%
master: 63%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 527.1 (CONTEXT=abs)

abs-lang / abs / 527 / 1 71% master: 63%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 527.1 (CONTEXT=abs)

abs-lang / abs / 527 / 1
71%
master: 63%

README BADGES
x