Skip to content

Commit aaff56c

Browse files
committed
Further edits for conciseness
1 parent 3c87cb4 commit aaff56c

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
@@ -1019,13 +1019,6 @@ Five alternatives are presented:
10191019
4. Allow both kinds of composition
10201020
5. Don't allow composition
10211021

1022-
Alternatives 2 and 3 were presented earlier in this document.
1023-
Alternative 4 is an idea from a prior mailing list discussion
1024-
of this problem. Alternative 1 is similar to Alternative 3
1025-
but introduces additional notation to make composition
1026-
easier to think about (which is why it's presented first).
1027-
Alternative 5 is included for completeness.
1028-
10291022
### Typed functions
10301023

10311024
Types are a way for users of a language
@@ -1139,8 +1132,6 @@ Consider (this suggestion is from Elango Cheran):
11391132
{{$x} {$y}}
11401133
```
11411134

1142-
1143-
11441135
`.pipeline` would be a new keyword that acts like `.local`,
11451136
except that if its expression has a function annotation,
11461137
the formatter would apply the "preservation model" semantics

0 commit comments

Comments
 (0)