Leandro Ostera

Yes, I think setting up the polyvariant errors as a default is a good idea to allow easy error return composition. I was thinking we can follow this pattern: https://github.com/ostera/reason-design-patterns/blob/master/patterns/polyvariant-error-propagation.md

That and the `let+/and+` syntax is fundamental to writing happy-paths without losing track of errors. Very much like Rust's `?` operator.

> @michallepicki For division by zero the plan is to panic like Ocaml does? Arithmetic and other runtime-provided functionality will end up having the semantics of the Erlang runtime. So...

Hello there! Thanks for opening the issue 🙏🏽 Just to set the right expectations This version of the compiler is no longer maintained. I have been working on a new...

The new compiler is a full rewrite that uses the OCaml Lambda and translates it directly into Core Erlang. It's also architected _so much better_, so onboarding into it, fixing...

@tmbb re: as many features as possible, I hear you. I think one example would be OCaml 5 effects -- this may be one of the features that are just...

The current `main` branch doesn't depend on my OCaml fork, but it also has several bugs that you'd have to work around. If you are interested in trying this out...

Thanks! It's probably a mistake in how we're bundling the version number into the final binary.

You could probably get away just by swapping the keyword from `import` to `include`, or potentially even a `pub` modifier on the entire `import`: ```gleam import project/foo.{print_foo} pub import project/foo.{...

Is "Users on other instances" basically anyone?