1. mookid11 Nov 9, 2024 parent

   you might like diffr (https://github.com/mookid/diffr) (disclaimer: my project)
2. mookid11 Mar 12, 2024 parent

   Matija Pretnar about the eff programming language and mathematical foundations for Effect Handlers.
3. 1 point Mar 12, 2024

   Mathematics Guides Effect Handlers [video]

   1 comment mookid11 youtube.com
4. mookid11 Jul 8, 2021 parent

   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 efficient (what about bugs in your parser? code with syntax errors? also, how fast would the parser be?)

   [0]: https://github.com/mookid/diffr

5. mookid11 Apr 27, 2020 parent

   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/diffr

6. mookid11 Apr 7, 2018 parent

   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 allows to reason about scope super easily; when you change scope, you just create a new map with the new variable bindings, and when the scope ends you just get back the map at the scope beginning which is still valid.

   With a stateful hashtable, you need to undo the changes you did in you scope; the value of the table when opening the scope that you want to get back to is gone forever. Now it ties you program to a certain execution order. One way to see that is that if you want to collect environment to each scope in some data structure for some reason, you need to make deep copies everywhere.

7. mookid11 Dec 4, 2017 parent

   > 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<>.

8. mookid11 Jul 28, 2017 parent

   It depends if you enjoy NullPointerExceptions.
9. mookid11 Jul 16, 2017 parent

   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 only need to break lines.

   And it can be pretty bad with haskell, which has complex semantics compared to, say, python.

   With whitespace sensitive syntax, I feel like in the dark age of manual indentation.

10. mookid11 Jul 16, 2017 parent

    > 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 Haskell makes it immediately worse. What a silly design.

11. mookid11 May 13, 2017 parent

    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 subroutines taking float arguments high.

12. mookid11 Mar 22, 2017 parent

    Interesting how the author avoids to mention OCaml's (far from perfect, but still) object system.
13. mookid11 Jan 31, 2017 parent

    I think this is the first time I see anyone like the OCaml syntax.
14. mookid11 Oct 30, 2016 parent

    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 slow to start.

    Also, don't forget C-M-{left, right, up, down} commands :)

15. mookid11 Sep 11, 2016 parent

    > 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 `Code reuse through polymorphic variants`.

16. mookid11 Aug 29, 2016 parent

    You can use the ocaml toolchain (for instance: ocamllex and ocamlyacc) and stop writing ad hoc parsers.
17. mookid11 Aug 29, 2016 parent

    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.

This user hasn’t submitted anything.