Re: To be or not to be - these are the options for Option.map

> Could you namedrop a few central modules (from Core) whose source code
one would be wise to read?

It of course depends on what you need, but let's state these:

Data Structures: List, Array, Map, Set, Hashtbl

Operations on basic types: Int, String

IO or other system operations: In_channel, Out_channel, Unix, Sys, Filename

Error handling: Error, Or_error
- probably you won't care about this at first, but lots of Core code itself
uses these so you might run into them

So far you've been asking about API documentation, but you can also read
Real World OCaml [1], and a couple of Jane Street's blog posts [2,3].

[1] https://realworldocaml.org/

[2] https://blogs.janestreet.com/how-to-fail-introducing-or-error-dot-t/
- but as I said, you probably won't care about this at first

[3] https://blogs.janestreet.com/maps-sets-and-hashtables-in-core/




On Sat, Sep 6, 2014 at 7:25 PM, [email protected] [ocaml_beginners] <
[email protected]> wrote:

>
>
>
>
>
> ---In [email protected], <yallop@...> wrote :
>
> Agreed -- the module-heavy style makes understanding difficult when
> you're unfamiliar with the library, since you often need to understand
> several modules in order to see what a simple function is doing. The
> corresponding benefit, though, is that you only need to understand a
> few modules thoroughly in order to understand the many things that you
> can build by combining them, so the work have to put in when you're
> getting started starts to pay off pretty quickly.
>
> Could you namedrop a few central modules (from Core) whose source code one
> would be wise to read?
>
>  
>