Ekdohibs
/
ocaml
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

PR#4881 typos 

git-svn-id: http://caml.inria.fr/svn/ocamldoc/trunk@10193 f963ae5c-01c2-4b8c-9fe0-0dff7051ff02
master
Damien Doligez 2009-10-02 09:14:34 +00:00
parent 1bdbffc77c
commit 1154875b5a
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
manual/manual/tutorials/lablexamples.etex
View File

@ -421,7 +421,7 @@ let eval2 eval = function
let rec eval x = eval2 eval x ;;
\end{caml_example}
To make this even more confortable, you may use type definitions as
To make this even more comfortable, you may use type definitions as
abbreviations for or-patterns. That is, if you have defined "type
myvariant = [`Tag1 int | `Tag2 bool]", then the pattern "#myvariant" is
equivalent to writing "(`Tag1(_ : int) | `Tag2(_ : bool))".
@ -448,7 +448,7 @@ let g = function
After seeing the power of polymorphic variants, one may wonder why
they were added to core language variants, rather than replacing them.
The answer is two fold. One first aspect is that while being pretty
The answer is twofold. One first aspect is that while being pretty
efficient, the lack of static type information allows for less
optimizations, and makes polymorphic variants slightly heavier than
core language ones. However noticeable differences would only