00:14 <zozozo> it actually depends on the shape of the code

07:14 <discocaml> <darrenldl> have dig back up the last issue i had on that type of stuff hmm

07:14 <discocaml> <darrenldl> have to*

08:37 <discocaml> <octachron> There are 6k files in the typechecker, so it is not only the size, but generated files tend to have extreme shape.

16:40 <discocaml> <cemerick> it sure would be nice to have a linter that complained on any non-function toplevel definition

16:41 <discocaml> <cemerick> it's too easy to let some bare value definition sneak into a change, and then blow up entire apps when it fails at startup time, etc

16:42 <discocaml> <masterbuilder> what do you mean?

16:44 <discocaml> <cemerick> @MasterBuilder when an e.g. dream app starts up, it's too easy for a top-level definition to fail (usually due to a configuration/environment problem) in un-graceful ways

16:44 <discocaml> <masterbuilder> so something with nontrivial initialization?

16:46 <discocaml> <cemerick> so I generally put such things in a promise that gets resolved by its consumer(s), and then you can have a very simple outer "shell" app that at least shows a reasonable message re: availability problems, logs the failure in ways that are better than a hard exn being raised when modules are being initialized, etc

16:46 <discocaml> <cemerick> could be very trivial! e.g. just not having a database connection string env var set properly, etc

16:48 <discocaml> <cemerick> but anyway, I had a lapse of discipline, and crashed an app this morning in an unfriendly way because I didn't get the runtime env config set up right to go along with a change that involved an eager top-level definition

16:49 <discocaml> <masterbuilder> yeah, that sucks

16:49 <discocaml> <masterbuilder> would a lint have really helped though? because it sounds like it was intentionally written that way and you would have ignored the warning

17:02 <discocaml> <geoff> locally, but perhaps the workflows on the remote repo could have errored out there

17:21 <discocaml> <შონია> Hello everyone) I have programming course in university and want to learn Ocaml as good as possible, what is the good way to start learning it?

17:28 <discocaml> <cemerick> ideally, the linter would need some kind of ignore annotation to pull one out of flow and realize the potential consequences, etc

17:37 <discocaml> <hopefullyhat> Is your university course using stdlib or Base/Core?

17:40 <discocaml> <შონია> I think base/core

17:41 <discocaml> <შონია> you mean without libraries yes?

17:41 <discocaml> <შონია> We do not use any libraries if you mean that, just Syntax, problems to solve using OCaml, modules, functors and some stuff

17:41 <discocaml> <შონია> Recursion on trees

17:56 <discocaml> <hopefullyhat> Base/Core are optional libraries that replace the standard library with slightly different and extended functionality

18:00 <discocaml> <შონია> Ah. I think we are learning pure ocaml

19:13 <discocaml> <leviroth> Does your course have any recommended resources?

19:13 <discocaml> <leviroth> Or a textbook?

19:18 <discocaml> <შონია> Mine? No. Only slides

19:59 <discocaml> <leviroth> https://johnwhitington.net/ocamlfromtheverybeginning/index.html is vanilla OCaml and I think well regarded.

21:13 <discocaml> <hopefullyhat> Also https://courses.cs.cornell.edu/cs3110/2021sp/textbook/basics/intro.html is great