Skip to content

Commit a95a03b

Browse files
committed
Further edits for conciseness
1 parent 3818c99 commit a95a03b

File tree

1 file changed

+0
-9
lines changed

1 file changed

+0
-9
lines changed

exploration/function-composition-part-1.md

Lines changed: 0 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -1009,13 +1009,6 @@ Five alternatives are presented:
10091009
4. Allow both kinds of composition
10101010
5. Don't allow composition
10111011

1012-
Alternatives 2 and 3 were presented earlier in this document.
1013-
Alternative 4 is an idea from a prior mailing list discussion
1014-
of this problem. Alternative 1 is similar to Alternative 3
1015-
but introduces additional notation to make composition
1016-
easier to think about (which is why it's presented first).
1017-
Alternative 5 is included for completeness.
1018-
10191012
### Typed functions
10201013

10211014
Types are a way for users of a language
@@ -1129,8 +1122,6 @@ Consider (this suggestion is from Elango Cheran):
11291122
{{$x} {$y}}
11301123
```
11311124

1132-
1133-
11341125
`.pipeline` would be a new keyword that acts like `.local`,
11351126
except that if its expression has a function annotation,
11361127
the formatter would apply the "preservation model" semantics

0 commit comments

Comments
 (0)