use named arguments in all sub-commands thanks to cmdliner monadic syntax #461
Conversation
|
cc @filipeom, you may be interested by this in other projects :-) |
I was just looking at this, and after reviewing the code, I can't understand why it's better this way (other than the fact that it looks more declarative and satisfying Could you briefly explain if there are any functional improvements to using the monadic syntax? I'm going to do this on smtml 😅 |
|
It allows named arguments, so you don't have to worry about the order anymore, which is nice when you have a lot of them! :) |
Ah yes, this is so cool! Thanks!! I'm using this everywhere moving forward 😅 |
As inspired by OCamlPro/owi#461: - use cmdliner's monadic syntax to build cmd terms; - use named arguments in the cmds functions. Other changes include: - Moving sub-commands into respective `cmd_<command_name>.ml` modules; - Creating a `Solver_mode` module; - Moving most functions from `Solver_dispatcher` into a more appropriate `Solver_type` module - Explicit exit codes for Term, Parse, and Exn error outputs in cmdliner.
As inspired by OCamlPro/owi#461: - use cmdliner's monadic syntax to build cmd terms; - use named arguments in the cmds functions. Other changes include: - Moving sub-commands into respective `cmd_<command_name>.ml` modules; - Creating a `Solver_mode` module; - Moving most functions from `Solver_dispatcher` into a more appropriate `Solver_type` module - Explicit exit codes for Term, Parse, and Exn error outputs in cmdliner.
No description provided.