Guides
Try and review the API¶
Start with a small calculation you know well. As you try the library, note what you expected, what happened, and where the API helped or got in the way. Those details make feedback easier to act on.
A short evaluation route¶
- Run the first program. Change the inputs and check that saved copies keep their values.
- Try integer division with negative operands, then compare it with exact fractions.
- Choose a Float precision and compare decimal text with input from a native float. Try complex arithmetic or ball bounds if your calculation needs them.
- Work through batches and selections, including a slice, a mask, and an overlapping assignment.
- Trigger an error and check the destination afterward.
- Save and restore a value through JSON, then try a conversion limit that is too small.
- Adapt counters and totals to your own inputs.
Key review criteria¶
| Area | Questions to consider |
|---|---|
| Construction | Is it clear which inputs are accepted and when they round? |
| Arithmetic | Are division rules, result types, and precision choices predictable? |
| Batches | Can you tell which shapes broadcast and which variable an update changes? |
| Errors | Does the message help you understand and fix the failed call? |
| Interchange | Do the text and JSON formats preserve the information you need? |
| Daily use | Can you express the calculation without depending on private storage details? |
Reporting feedback and edge cases¶
For a bug report, include:
- A small, self-contained Mojo program that shows the problem.
- The expected result and the actual output or error.
- The compiler version from
pixi run --locked mojo --version. - Any relevant precision, rounding mode, shape, or conversion limits.
For an API suggestion, show the call you would like to write and how it would help your calculation. Before reporting an issue, check support and limitations for known boundaries.