reasonml-old / wiki Goto Github PK

E.g. one missing piece I quickly encountered was the lack of an Option module.

So should we go with Core or Batteries Included, or should there be an entirely separate bs core library? And how do you set this up and get it working?

I imagine the various js unit test frameworks will be a challenge to port over in any ergonomic way. So... OUnit?

1. Should names be js-y (forEach) or ml-y (for_each)? Reason is going for js-y, and the npm ecosystem is obviously js-y, yet many bindings seem to go for ml-y naming.
2. What about file naming? BS has some constraints here, e.g. no dasherized filenames allowed.
3. Standard prefix or postfix for module signatures? E.g. IModule, Module_Sig or MODULE
4. Should types follow the same convention as functions and variables, or be different?
5. Constants?
6. Prefer short names for brevity or long names for clarity?
7. Should comments be placed before or after the code they address.
8. Tabs or spaces? 2 or 4 spaces per indent level?
9. Prefer piping or intermediate let bindings?
10. Prefer labeled and optional arguments when several arguments have same type? Append a unit argument when all arguments are labeled?
11. Prefer let f : int -> string = fun x ->... over let f (x: int): string = ...?
12. Place vertical bar | indented or leveled with the enclosing structure in variant defintions, match expressions and piping?
13. How to break long lines?
14. Exit branches first or last in a pattern match?
15. Named convention for "overloading" externals (#4 (comment))
16. Naming convention for list destructuring (#4 (comment))

@chenglou I think we can kill this now. The content has (mostly) been moved to the new website. See
reasonml/reasonml.github.io#133
reasonml/reasonml.github.io#135
reasonml/reasonml.github.io#134

etcetc