@jorenham sir I tried running this locally and got results with different lengths like (0,) for size 1 and others for size 2). I used ... to be safe since it seems variable, but please let me know if there's a better way to handle that.

Also, I noticed the CLI checks failed on the existing tests—should I just update those files to match this new type?

I tried running this locally and got results with different lengths like (0,) for size 1 and others for size 2). I used ... to be safe since it seems variable, but please let me know if there's a better way to handle that.

Ah I see... It's a bit unfortunate, but nothing to lose sleep over 🤷. Anyway, tuple[int, ...] is then indeed the right way to go here

Also, I noticed the CLI checks failed on the existing tests—should I just update those files to match this new type?

Yea it's better to update those instead of writing new ones then.

@jorenham sir Expert advice needed! 🏳️

The Linter and Formatter seem to be at war over these long lines. Every time I appease one, the other gets angry. 🤯

The Linter and Formatter seem to be at war over these long lines. Every time I appease one, the other gets angry. 🤯

Running uv run ruff check --fix could help

The Linter and Formatter seem to be at war over these long lines. Every time I appease one, the other gets angry. 🤯

Running uv run ruff check --fix could help

Done

Thanks @pareshjoshij