[variable-length-quantity] Testing overflow of `u32`?

Exercism
1

I’m currently updating variable-length-quantity on the Rust track with problem-specifications. Our stub has an enum for error handling, one variant for incomplete sequences (which is tested by canonical data), and another variant for overflow.

The exercise instructions state:

Although VLQ can deal with numbers of arbitrary sizes, for this exercise we will restrict ourselves to only numbers that fit in a 32-bit unsigned integer.

What is most appropriate here? Should I upstream the tests for overflow? Or is this out of scope for the exercise and I should drop these tests on the Rust track too? (This would be a backwards-compatible change I believe.) Or should I maintain these additional tests as they are?

2

I mean I think it is valuable to know how to handle overflow / avoid overflow, my experience on the rust track was that there was quite a few exercises practicing that, (I think Triangle does) so I wouldn’t say there is something wrong with reducing the amount of exercises practicing that. But I wouldn’t remove it from all exercises