coverage: 98.946%. remained the same
when pulling 7edff86 on LucaDiba:constructCell-cli
into 1de1552 on uber:master.

This is great. Thanks @LucaDiba!

Would you also be able to add a short description for the CLI in the docs (which I skipped in #1077, because I wasn't sure what the final API would look like)?

Would you also be able to add a short description for the CLI in the docs (which I skipped in #1077, because I wasn't sure what the final API would look like)?

Yup, updated.

Here's a thought: What about making the resolution parameter optional? We can infer the res from the length of the digits.

I'm raising it here because I'm considering doing something like that for the Python bindings.

Another solution would be to not have a resolution parameter at all, and just read from the length of the digits. That's not so different from what, say, compactCells does in the CLI; we don't pass in the number of cells. The res parameter is redundant if you have another way to know the length of the list.

Here's a thought: What about making the resolution parameter optional? We can infer the res from the length of the digits.

I'm raising it here because I'm considering doing something like that for the Python bindings.

Another solution would be to not have a resolution parameter at all, and just read from the length of the digits. That's not so different from what, say, compactCells does in the CLI; we don't pass in the number of cells. The res parameter is redundant if you have another way to know the length of the list.

I would be fine with optional, as long as an explicit mismatch results in an error. It can be useful to have it automatically inferred when using it manually, but including the resolution inside of a batch scripting job so that you can find corrupt input data.

Here's a thought: What about making the resolution parameter optional? We can infer the res from the length of the digits.

I would be fine with optional, as long as an explicit mismatch results in an error. It can be useful to have it automatically inferred when using it manually, but including the resolution inside of a batch scripting job so that you can find corrupt input data.

Makes sense, I like this approach. Updated.