Viewing profile — mookid11

you might like diffr ( https://github.com/mookid/diffr ) (disclaimer: my project)

Matija Pretnar about the eff programming language and mathematical foundations for Effect Handlers.

I wrote diffr [0] for that purpose; it serves me well, especially if your team makes code with long lines. In my opinion, a simple approach that does NOT make any parsing is more e…

Sort of related: as I never made diff-highlight work correctly on Windows, I wrote diffr[0] which goes a little bit behond what diff-highlight does. [0]: https://github.com/mookid/…

The point is to share intermediate state of your data structure without headache. For instance, if you write an interpreter, representing variable bindings with a functional map al…

> For example, you'd not get far in Rust without Result , Option or Future which are all make use of delayed resolution for their value. Certainly not for Result or Option .

It depends if you enjoy NullPointerExceptions.

Unless experienced, you have no clue how a piece of code will be parsed. With ocaml, where is very little ambiguity; and indentation tools can take care of proper formatting, you o…

> Haskell has some nice things going for it. Its syntax is cleaner than OCaml's, for example. While I find the ocaml syntax very far from perfect, the whitespace sensitivity of Has…

To allow IEEE compliant float with tagged pointers. However, note that floats are not boxed in the OCaml's arrays. Boxing floats is a pain because it makes the price of defining su…

Interesting how the author avoids to mention OCaml's (far from perfect, but still) object system.

I think this is the first time I see anyone like the OCaml syntax.

I think that you only need isearch + occur (M-s .), not ace-jump. I tried ace-jump and have it configured for months, I never use it. neither do I use swiper, because it is too slo…

> Yes, but hardly anybody uses that part of the language. We tend to stick with modules and variations over them. You can have inheritance via polymorphic variants: see Garrigue's …

You can use the ocaml toolchain (for instance: ocamllex and ocamlyacc) and stop writing ad hoc parsers.

I like: http://caml.inria.fr/pub/docs/oreilly-book Real world ocaml is not so complete, and light on subjects such as C interop.