Skip to content
This repository was archived by the owner on Jan 26, 2022. It is now read-only.

Commit 87e6ffc

Browse files
js-choijs-choi
committed
Update intros to all Markdown documents
Remove unnecessary tables of contents.
1 parent a7451b7 commit 87e6ffc

13 files changed

+28
-119
lines changed

‎additional-feature-ba.md

+2-8
Original file line numberDiff line numberDiff line change
@@ -8,15 +8,9 @@
88
|[Additional Feature TS][]| None | Pipeline `try` statements | Tacit application to **caught errors** |
99
|[Additional Feature NP][]| None | N-ary pipelines `(…, …) \|> …`<br>Lexical topics `##`, `###`, and `...`| **N-ary** function/expression **application** |
1010

11-
<!-- START doctoc generated TOC please keep comment here to allow auto update -->
12-
<!-- DON'T EDIT THIS SECTION, INSTEAD RE-RUN doctoc TO UPDATE -->
13-
14-
15-
- [Additional Feature BA](#additional-feature-ba)
16-
17-
<!-- END doctoc generated TOC please keep comment here to allow auto update -->
18-
1911
# Additional Feature BA
12+
ECMAScript No-Stage Proposal. Living Document. J. S. Choi, 2018-12.
13+
2014
An feature – **bare awaited calls** – makes async function calls terser. It adds
2115
another mode to bare style: if a bare-style pipeline step is preceded by a
2216
`await`, then instead of a mere function call, it is an awaited function call.

‎additional-feature-bc.md

+2-8
Original file line numberDiff line numberDiff line change
@@ -8,15 +8,9 @@
88
|[Additional Feature TS][]| None | Pipeline `try` statements | Tacit application to **caught errors** |
99
|[Additional Feature NP][]| None | N-ary pipelines `(…, …) \|> …`<br>Lexical topics `##`, `###`, and `...`| **N-ary** function/expression **application** |
1010

11-
<!-- START doctoc generated TOC please keep comment here to allow auto update -->
12-
<!-- DON'T EDIT THIS SECTION, INSTEAD RE-RUN doctoc TO UPDATE -->
13-
14-
15-
- [Additional Feature BC](#additional-feature-bc)
16-
17-
<!-- END doctoc generated TOC please keep comment here to allow auto update -->
18-
1911
# Additional Feature BC
12+
ECMAScript No-Stage Proposal. Living Document. J. S. Choi, 2018-12.
13+
2014
An additional feature – **bare constructor calls** – makes constructor calls
2115
terser. It adds a mode to bare style: if a bare-style pipeline step is preceded
2216
by a `new`, then instead of a function call, it is a constructor call. `value |>

‎additional-feature-bp.md

+2-11
Original file line numberDiff line numberDiff line change
@@ -8,18 +8,9 @@
88
|[Additional Feature TS][]| None | Pipeline `try` statements | Tacit application to **caught errors** |
99
|[Additional Feature NP][]| None | N-ary pipelines `(…, …) \|> …`<br>Lexical topics `##`, `###`, and `...`| **N-ary** function/expression **application** |
1010

11-
<!-- START doctoc generated TOC please keep comment here to allow auto update -->
12-
<!-- DON'T EDIT THIS SECTION, INSTEAD RE-RUN doctoc TO UPDATE -->
13-
14-
15-
- [Additional Feature BP](#additional-feature-bp)
16-
- [WHATWG Fetch Standard (Core Proposal + Additional Feature BP)](#whatwg-fetch-standard-core-proposal--additional-feature-bp)
17-
- [jQuery (Core Proposal + Additional Feature BP)](#jquery-core-proposal--additional-feature-bp)
18-
- [Lodash (Core Proposal + Additional Feature BP)](#lodash-core-proposal--additional-feature-bp)
19-
20-
<!-- END doctoc generated TOC please keep comment here to allow auto update -->
21-
2211
# Additional Feature BP
12+
ECMAScript No-Stage Proposal. Living Document. J. S. Choi, 2018-12.
13+
2314
There is a TC39 proposal for [`do` expressions][] at Stage 1. Smart pipelines do
2415
**not** require `do` expressions. However, if [`do` expressions][] also become
2516
part of JavaScript, then, as with **any** other type of expression, a pipeline

‎additional-feature-np.md

+3-12
Original file line numberDiff line numberDiff line change
@@ -8,19 +8,10 @@
88
|[Additional Feature TS][]| None | Pipeline `try` statements | Tacit application to **caught errors** |
99
|[Additional Feature NP][]| None | N-ary pipelines `(…, …) \|> …`<br>Lexical topics `##`, `###`, and `...`| **N-ary** function/expression **application** |
1010

11-
<!-- START doctoc generated TOC please keep comment here to allow auto update -->
12-
<!-- DON'T EDIT THIS SECTION, INSTEAD RE-RUN doctoc TO UPDATE -->
13-
14-
15-
- [Additional Feature NP](#additional-feature-np)
16-
- [Lodash (Core Proposal + Additional Features BP+PP+PF+NP)](#lodash-core-proposal--additional-features-bppppfnp)
17-
- [Ramda (Core Proposal + Additional Features BP+PF+NP)](#ramda-core-proposal--additional-features-bppfnp)
18-
- [WHATWG Streams Standard (Core Proposal + Additional Features BP+PP+PF+NP)](#whatwg-streams-standard-core-proposal--additional-features-bppppfnp)
19-
20-
<!-- END doctoc generated TOC please keep comment here to allow auto update -->
21-
2211
# Additional Feature NP
23-
Another Additional Feature – **n-ary pipelines** – enables the passing of
12+
ECMAScript No-Stage Proposal. Living Document. J. S. Choi, 2018-12.
13+
14+
An Additional Feature – **n-ary pipelines** – enables the passing of
2415
multiple arguments into a pipeline’s steps. `(a, b) |> f` is equivalent to
2516
`f(a, b)`, and `a |> (f(#), g(#)) |> h` is equivalent to `h(f(a), g(a))`.
2617

‎additional-feature-pf.md

+2-10
Original file line numberDiff line numberDiff line change
@@ -8,17 +8,9 @@
88
|[Additional Feature TS][]| None | Pipeline `try` statements | Tacit application to **caught errors** |
99
|[Additional Feature NP][]| None | N-ary pipelines `(…, …) \|> …`<br>Lexical topics `##`, `###`, and `...`| **N-ary** function/expression **application** |
1010

11-
<!-- START doctoc generated TOC please keep comment here to allow auto update -->
12-
<!-- DON'T EDIT THIS SECTION, INSTEAD RE-RUN doctoc TO UPDATE -->
13-
14-
15-
- [Additional Feature PF](#additional-feature-pf)
16-
- [Ramda (Core Proposal + Additional Feature BP+PF)](#ramda-core-proposal--additional-feature-bppf)
17-
- [WHATWG Streams Standard (Core Proposal + Additional Features BP+PP+PF)](#whatwg-streams-standard-core-proposal--additional-features-bppppf)
18-
19-
<!-- END doctoc generated TOC please keep comment here to allow auto update -->
20-
2111
# Additional Feature PF
12+
ECMAScript No-Stage Proposal. Living Document. J. S. Choi, 2018-12.
13+
2214
**More than any other** possible extension in this table, this additional
2315
feature – **Pipeline Functions** – would dramatically increase the usefulness of
2416
pipelines. It introduces just one additional operator that solves:\

‎additional-feature-ts.md

+2-8
Original file line numberDiff line numberDiff line change
@@ -8,15 +8,9 @@
88
|[Additional Feature TS][]| None | Pipeline `try` statements | Tacit application to **caught errors** |
99
|[Additional Feature NP][]| None | N-ary pipelines `(…, …) \|> …`<br>Lexical topics `##`, `###`, and `...`| **N-ary** function/expression **application** |
1010

11-
<!-- START doctoc generated TOC please keep comment here to allow auto update -->
12-
<!-- DON'T EDIT THIS SECTION, INSTEAD RE-RUN doctoc TO UPDATE -->
13-
14-
15-
- [Additional Feature TS](#additional-feature-ts)
16-
17-
<!-- END doctoc generated TOC please keep comment here to allow auto update -->
18-
1911
# Additional Feature TS
12+
ECMAScript No-Stage Proposal. Living Document. J. S. Choi, 2018-12.
13+
2014
With the [Core Proposal][] only, all `try` statements’ `catch` clauses would
2115
prohibit the use of the topic reference within their steps, except where the
2216
topic reference `#` is inside an inner pipeline inside the `catch` clause: this

‎core-real-examples.md

+1
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,5 @@
11
# Core Proposal real-world examples
2+
Living Document. J. S. Choi, 2018-12.
23

34
### WHATWG Fetch Standard
45
The [WHATWG Fetch Standard][] contains several examples of using the DOM `fetch`

‎core-syntax.md

+2
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,6 @@
11
# Core-proposal syntax
2+
ECMAScript Stage-0 Proposal. Living Document. J. S. Choi, 2018-12.
3+
24
Most pipeline steps will use topic references in their steps. This style of
35
pipeline step is called **[topic style][]**.
46

‎goals.md

+2-33
Original file line numberDiff line numberDiff line change
@@ -1,37 +1,6 @@
1-
<!-- START doctoc generated TOC please keep comment here to allow auto update -->
2-
<!-- DON'T EDIT THIS SECTION, INSTEAD RE-RUN doctoc TO UPDATE -->
3-
4-
5-
- [Goals](#goals)
6-
- [“Don’t break my code.”](#dont-break-my-code)
7-
- [Backward compatibility](#backward-compatibility)
8-
- [Zero runtime cost](#zero-runtime-cost)
9-
- [Forward compatibility](#forward-compatibility)
10-
- [“Don’t shoot me in the foot.”](#dont-shoot-me-in-the-foot)
11-
- [Opt-in behavior](#opt-in-behavior)
12-
- [Simple scoping](#simple-scoping)
13-
- [Static analyzability](#static-analyzability)
14-
- [“Don’t make me overthink.”](#dont-make-me-overthink)
15-
- [Syntactic locality](#syntactic-locality)
16-
- [Semantic clarity](#semantic-clarity)
17-
- [Expressive versatility](#expressive-versatility)
18-
- [Cyclomatic simplicity](#cyclomatic-simplicity)
19-
- [“Make my code easier to read.”](#make-my-code-easier-to-read)
20-
- [Untangled flow](#untangled-flow)
21-
- [Distinguishable punctuators](#distinguishable-punctuators)
22-
- [Terse parentheses](#terse-parentheses)
23-
- [Terse variables](#terse-variables)
24-
- [Terse function calls](#terse-function-calls)
25-
- [Terse composition](#terse-composition)
26-
- [Terse partial application](#terse-partial-application)
27-
- [Other Goals](#other-goals)
28-
- [Conceptual generality](#conceptual-generality)
29-
- [Human writability](#human-writability)
30-
- [Novice learnability](#novice-learnability)
31-
32-
<!-- END doctoc generated TOC please keep comment here to allow auto update -->
33-
341
# Goals
2+
Living Document. J. S. Choi, 2018-12.
3+
354
There are seventeen ordered goals that the smart step syntax tries to fulfill,
365
which may be summarized,\
376
“Don’t break my code,”\

‎license.md

-8
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,3 @@
1-
<!-- START doctoc generated TOC please keep comment here to allow auto update -->
2-
<!-- DON'T EDIT THIS SECTION, INSTEAD RE-RUN doctoc TO UPDATE -->
3-
4-
5-
- [MIT License](#mit-license)
6-
7-
<!-- END doctoc generated TOC please keep comment here to allow auto update -->
8-
91
# MIT License
102

113
Copyright © 2018 J. S. Choi.

‎nomenclature.md

-8
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,3 @@
1-
<!-- START doctoc generated TOC please keep comment here to allow auto update -->
2-
<!-- DON'T EDIT THIS SECTION, INSTEAD RE-RUN doctoc TO UPDATE -->
3-
4-
5-
- [Explanation of nomenclature](#explanation-of-nomenclature)
6-
7-
<!-- END doctoc generated TOC please keep comment here to allow auto update -->
8-
91
# Explanation of nomenclature
102
The term [“**topic**” comes from linguistics][topic and comment] and have
113
precedent in prior programming languages’ use of “topic variables”.

‎relations.md

+8-1
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,9 @@
1+
# Relations to other work
2+
Living Document. J. S. Choi, 2018-12.
3+
4+
<details>
5+
<summary>Table of contents</summary>
6+
17
<!-- START doctoc generated TOC please keep comment here to allow auto update -->
28
<!-- DON'T EDIT THIS SECTION, INSTEAD RE-RUN doctoc TO UPDATE -->
39

@@ -20,7 +26,8 @@
2026

2127
<!-- END doctoc generated TOC please keep comment here to allow auto update -->
2228

23-
# Relations to other work
29+
</details>
30+
2431
## Pipelines in other programming languages
2532
The concept of a pipe operator appears in numerous other languages, variously
2633
called “pipeline”, “threading”, and “feed” operators. This is because developers

‎term-rewriting.md

+2-12
Original file line numberDiff line numberDiff line change
@@ -1,16 +1,6 @@
1-
<!-- START doctoc generated TOC please keep comment here to allow auto update -->
2-
<!-- DON'T EDIT THIS SECTION, INSTEAD RE-RUN doctoc TO UPDATE -->
3-
4-
5-
- [Term rewriting](#term-rewriting)
6-
- [Core Proposal](#core-proposal)
7-
- [Additional Feature BP](#additional-feature-bp)
8-
- [Additional Feature NP](#additional-feature-np)
9-
- [Smart body syntax](#smart-body-syntax)
10-
11-
<!-- END doctoc generated TOC please keep comment here to allow auto update -->
12-
131
# Term rewriting
2+
Living Document. J. S. Choi, 2018-12.
3+
144
## Core Proposal
155
Pipelines can be rewritten into a nested [`do` expression][]. There are
166
many ways to illustrate this equivalency. (It can also be less simply rewritten

0 commit comments

Comments
 (0)