X-Git-Url: http://lambda.jimpryor.net/git/gitweb.cgi?p=lambda.git;a=blobdiff_plain;f=code%2Fgsv2.ml;h=7f2775a7994dcc23e3e516b81523e17f638b7ca5;hp=8a9c13728ad4699bdd02beb3ea0e3abb109e68bf;hb=ad14f269d489cc9a2ea9e522e2da37a42cfd46b3;hpb=d377c75972d3c853a881da505aa129eb7d363186 diff --git a/code/gsv2.ml b/code/gsv2.ml index 8a9c1372..7f2775a7 100644 --- a/code/gsv2.ml +++ b/code/gsv2.ml @@ -1021,7 +1021,7 @@ module Sem8f = struct [topic] as our payloads, so that sent types would then be: [topic] -> S'Y([topic]). All of the operations except for `maybe` would then have to emulate the operations of the List monad by hand (manually performing catmap etc). But `maybe` could examine the [topic] as a whole and decide whether to return box(it) or box([]). - This would be to go back to the Sem4/Sem5 choices of monads (without list), and to implement the handling of lists + This would be to go back to the Sem5/Sem6 choices of monads (without list), and to implement the handling of lists by hand, as we did in the Sem1/Sem2 strategies. Additionally, we haven't tried here to handle non-rigid noun-types. That's why we can have sent types be: @@ -1053,21 +1053,21 @@ module TestAll = struct print_endline "\nTesting Sem1b";; module T1b = Test(Sem1b);; print_endline "\nTesting Sem3a";; - module T2a = Test(Sem3a);; + module T3a = Test(Sem3a);; print_endline "\nTesting Sem3c";; - module T2c = Test(Sem3c);; + module T3c = Test(Sem3c);; print_endline "\nTesting Sem4a";; - module T3a = Test(Sem4a);; + module T4a = Test(Sem4a);; print_endline "\nTesting Sem4c";; - module T3c = Test(Sem4c);; + module T4c = Test(Sem4c);; print_endline "\nTesting Sem7c";; - module T5c = Test(Sem7c);; + module T7c = Test(Sem7c);; print_endline "\nTesting Sem7f";; - module T5e = Test(Sem7f);; + module T7f = Test(Sem7f);; print_endline "\nTesting Sem8c";; - module T6c = Test(Sem8c);; + module T8c = Test(Sem8c);; print_endline "\nTesting Sem8f";; - module T6e = Test(Sem8f);; + module T8f = Test(Sem8f);; print_newline () end