diff options
| author | Kartik K. Agaram <vc@akkartik.com> | 2015-11-10 21:49:05 -0800 |
|---|---|---|
| committer | Kartik K. Agaram <vc@akkartik.com> | 2015-11-10 21:53:35 -0800 |
| commit | 162f21b818a3ac8124741ddb91c48df140aea55a (patch) | |
| tree | f7fd929cc686b64a7a9c2e9a152d700a4c5ed49a | |
| parent | 76755b2836b0dadd88f82635f661f9d9df77604d (diff) | |
| download | mu-162f21b818a3ac8124741ddb91c48df140aea55a.tar.gz | |
2424
| -rw-r--r-- | 058shape_shifting_container.cc | 11 | ||||
| -rw-r--r-- | html/058shape_shifting_container.cc.html | 11 |
2 files changed, 6 insertions, 16 deletions
diff --git a/058shape_shifting_container.cc b/058shape_shifting_container.cc index 1a58b1b6..1f0acab9 100644 --- a/058shape_shifting_container.cc +++ b/058shape_shifting_container.cc @@ -1,14 +1,9 @@ //:: Container definitions can contain type parameters. //: -//: Extremely hacky initial implementation: -//: -//: a) We still don't support the full complexity of type trees inside -//: container definitions. So for example you can't have a container element -//: with this type: +//: Extremely hacky initial implementation. We still don't support the full +//: complexity of type trees inside container definitions. So for example you +//: can't have a container element with this type: //: (map (array address character) (list number)) -//: -//: b) We also can't include type parameters anywhere except at the top of the -//: type of a container element. :(scenario size_of_shape_shifting_container) container foo:_t [ diff --git a/html/058shape_shifting_container.cc.html b/html/058shape_shifting_container.cc.html index 4425953a..4a4fb2cc 100644 --- a/html/058shape_shifting_container.cc.html +++ b/html/058shape_shifting_container.cc.html @@ -34,15 +34,10 @@ body { font-family: monospace; color: #eeeeee; background-color: #080808; } <pre id='vimCodeElement'> <span class="SalientComment">//:: Container definitions can contain type parameters.</span> <span class="Comment">//:</span> -<span class="Comment">//: Extremely hacky initial implementation:</span> -<span class="Comment">//:</span> -<span class="Comment">//: a) We still don't support the full complexity of type trees inside</span> -<span class="Comment">//: container definitions. So for example you can't have a container element</span> -<span class="Comment">//: with this type:</span> +<span class="Comment">//: Extremely hacky initial implementation. We still don't support the full</span> +<span class="Comment">//: complexity of type trees inside container definitions. So for example you</span> +<span class="Comment">//: can't have a container element with this type:</span> <span class="Comment">//: (map (array address character) (list number))</span> -<span class="Comment">//:</span> -<span class="Comment">//: b) We also can't include type parameters anywhere except at the top of the</span> -<span class="Comment">//: type of a container element.</span> <span class="Delimiter">:(scenario size_of_shape_shifting_container)</span> container foo:_t [ |