Commit Graph

15 Commits

Author SHA1 Message Date
Sean Hellum
147b9d4436
Add Better-TOML (#1417) 2020-02-19 16:59:42 -05:00
Sean Hellum
bc5a969562 [Gitpod] Add some VSCode extensions (#1268)
VSCode extensions for productive work.
2020-01-23 00:51:08 -05:00
Sean Hellum
fb977ab941 add automated setup badge and add .gitpod.yml patch (#1246)
* add automated setup badge and add .gitpod.yml patch

* Update .gitpod.yml
2020-01-20 14:40:04 +13:00
Yehuda Katz
e8800fdd0c Remove the coloring_in_tokens feature flag
Stabilize and enable
2019-12-12 11:34:43 -08:00
Yehuda Katz
57af9b5040 Add Range and start Signature support
This commit contains two improvements:

- Support for a Range syntax (and a corresponding Range value)
- Work towards a signature syntax

Implementing the Range syntax resulted in cleaning up how operators in
the core syntax works. There are now two kinds of infix operators

- tight operators (`.` and `..`)
- loose operators

Tight operators may not be interspersed (`$it.left..$it.right` is a
syntax error). Loose operators require whitespace on both sides of the
operator, and can be arbitrarily interspersed. Precedence is left to
right in the core syntax.

Note that delimited syntax (like `( ... )` or `[ ... ]`) is a single
token node in the core syntax. A single token node can be parsed from
beginning to end in a context-free manner.

The rule for `.` is `<token node>.<member>`. The rule for `..` is
`<token node>..<token node>`.

Loose operators all have the same syntactic rule: `<token
node><space><loose op><space><token node>`.

The second aspect of this pull request is the beginning of support for a
signature syntax. Before implementing signatures, a necessary
prerequisite is for the core syntax to support multi-line programs.

That work establishes a few things:

- `;` and newlines are handled in the core grammar, and both count as
  "separators"
- line comments begin with `#` and continue until the end of the line

In this commit, multi-token productions in the core grammar can use
separators interchangably with spaces. However, I think we will
ultimately want a different rule preventing separators from occurring
before an infix operator, so that the end of a line is always
unambiguous. This would avoid gratuitous differences between modules and
repl usage.

We already effectively have this rule, because otherwise `x<newline> |
y` would be a single pipeline, but of course that wouldn't work.
2019-12-11 16:41:07 -08:00
Sean Hellum
f2968c8385
Update .gitpod.yml 2019-12-01 17:16:53 -06:00
Sean Hellum
b39c2e2f75 edit install cmd 2019-11-11 18:17:55 +00:00
Sean Hellum
3b84e3ccfe
Update .gitpod.yml 2019-11-04 11:44:56 -06:00
Sean Hellum
78ccd4181c
Update .gitpod.yml 2019-09-27 21:46:04 -05:00
Blurryface05
b4c783f23d modified: .gitpod.yml 2019-09-28 01:18:55 +00:00
Blurryface05
6f6d2abdac modified: .gitpod.yml 2019-09-28 01:18:00 +00:00
Sean Hellum
20de0ea01f
Update .gitpod.yml 2019-09-27 20:09:21 -05:00
Sean Hellum
12f34cc698
Update .gitpod.yml 2019-09-27 19:54:42 -05:00
Sean Hellum
ac116f4f7c
Update .gitpod.yml 2019-09-27 19:54:05 -05:00
Blurryface05
1da6ac8de7 i
new file:   .gitpod.Dockerfile
	new file:   .gitpod.yml
2019-09-27 23:01:34 +00:00