Re: To be or not to be - these are the options for Option.map
| Newsgroups | gmane.comp.lang.ocaml.beginners |
|---|---|
| Message-ID | <CAAxsn=EktyUp3=LY0C70tUU5Vd2VpK-C3S0iWU6-2oVD0CD+_g@mail.gmail.com> |
On 6 September 2014 18:04, Ashish Agarwal [email protected] [ocaml_beginners] <[email protected]> wrote: > deficiencies in the tool that generates documentation (there is hopefully a new project to improve this) Yes: we're working on this at OCaml Labs. Anil's talk at OCaml 2014 yesterday had some details: https://www.youtube.com/watch?v=jxhtpQ5nJHg&t=13m44s > Core's heavy factoring of code into various sub-modules and functors (this is a good thing as it also makes Core very robust and maintainable, but unfortunately is often contrary to what a human needs to understand the code) 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.