Removed Type-Defect label.
Added Type-Enhancement, Area-Library, Triaged labels.

But that would only work for small numbers.
divmod is something that is pretty useful for bignums too. It would be a shame if uint32s and bignums didn't share the same interface.

This comment was originally written by @tatumizer

Yes, you are right. I don't know how to do it syntactically, that's the
problem. Maybe introduce class DivMod, but in such manner that the instance
we create once, can be reused for iterative divisions. I don't know the
best format of it, can't find any pattern that does something similar.

This comment was originally written by @tatumizer

If dart compiler learns how to inline callbacks, we can do simply this:
divmod(a, 10, (q,r) { /*do something with q, r *})

and we can use same pattern everywhere where we need to return several
values.
But it should be inlined. Maybe this is ok?

I am not in favor of adding divMod. It should be straightforward and likely more efficient to optimize code so that only one division is issued where possible.

This comment was originally written by @tatumizer

Upon more thinking, I tend to agree. One division and one multiplication is
needed to find both q and r. this multiplication is eliminated in divMod,
but there will be certain overhead in divMod anyay.
Multiplication is relatively cheap operation these days, so we won't get
too much benefit.

This comment was originally written by @tatumizer

Please close the issue, it's fixed already for all kinds of ints. (Compiler recognizes the pattern x/y followed by x%y and vice versa and generates only one division)