Carl Mäsak

Developer guide

1

Somewhat connected to #385, I guess. I just stumbled over [the Mozilla developer guide (introduction)](https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Introduction). It's inspiring. If we make ours half as inspiring as that, we're in a good...

We don't have too many things on our wishlist describing changes to the compilation process itself, so here's one: importing a module to forbid potentially infinite loops and recursion: ```...

Implement safe navigation/null-coalescing operator

2

Code like this: my bossName; if employee != None { if employee.boss != None { bossName = employee.boss.name; } else { bossName = None; } } else { bossName =...

tbd

tbd

Implement CHECK blocks

1

We already have the concept of `CHECK` time in 007, so it makes sense to have `CHECK` blocks too.

Add a "style guide" to the documentation

1

Kind of [PEP 8](https://www.python.org/dev/peps/pep-0008/)-ish or [perlstyle](https://perldoc.perl.org/perlstyle.html)-oid. Needless to say, this would go really well together with the idea of a [prettier](https://prettier.io/)-style tool, already outlined in https://github.com/masak/007/issues/14#issuecomment-149211379.

Get rid of .prefix and .suffix, and implement .startsWith and .endsWith instead

1

Basically those two are what one tends to want to reach for when working with strings (at least until we have regex matching in the language). The issue that introduced...

In the fullness of time we probably want many of the phasers of Perl 6, but this one seems like easy pickings.

Unable to declare infix:<..>

2

``` $ bin/007 -e='func infix:(low, high) { [] }; say(1 .. 2)' Could not parse program ``` Pretty sure parsing of `postfix:` is messing with the custom operator here. But...