|
@@ -22,18 +22,16 @@ content: |
|
|
Thule aims to pull those low-level building blocks out, so the
|
|
Thule aims to pull those low-level building blocks out, so the
|
|
output from `ls` might give you a collection like
|
|
output from `ls` might give you a collection like
|
|
|
|
|
|
- ~~~~
|
|
|
|
- (set (file "/tmp/foo.txt") (file "/tmp/bar.c"))
|
|
|
|
- ~~~~
|
|
|
|
|
|
+ (set (file "/tmp/foo.txt") (file "/tmp/bar.c"))
|
|
|
|
|
|
and the output from `wc` will give you
|
|
and the output from `wc` will give you
|
|
|
|
|
|
- ~~~~
|
|
|
|
|
|
+
|
|
(table ("lines" "words" "characters" "file")
|
|
(table ("lines" "words" "characters" "file")
|
|
((int 10) (int 30) (int 300) (file "/tmp/foo.txt"))
|
|
((int 10) (int 30) (int 300) (file "/tmp/foo.txt"))
|
|
((int 20) (int 60) (int 900) (file "/tmp/bar.c"))
|
|
((int 20) (int 60) (int 900) (file "/tmp/bar.c"))
|
|
((int 30) (int 90) (int 1200) (text "total")))
|
|
((int 30) (int 90) (int 1200) (text "total")))
|
|
- ~~~~
|
|
|
|
|
|
+
|
|
|
|
|
|
Both of these would not be displayed in a raw way by the shell, but
|
|
Both of these would not be displayed in a raw way by the shell, but
|
|
rather the structure of the collections would be a hint to the
|
|
rather the structure of the collections would be a hint to the
|