[stdlib] Audit uses of `StaticIntTuple` about mojo HOT 8 OPEN

@msaelices it's ongoing changes, you can take a look at #2335

from mojo.

I propose to use 'NTuple[2, Int]' as the type alias for 'Tuple[Int, Int]', and 'NTuple[N, T]' in general, so that it can be easily dispatch on 'N'.

from mojo.

I propose to use 'NTuple[2, Int]' as the type alias for 'Tuple[Int, Int]', and 'NTuple[N, T]' in general, so that it can be easily dispatch on 'N'.

Can you elaborate on the value of the type alias? I'm not sure I understand the full value yet. Are there places you have in mind in the library that would benefit from this?

from mojo.

NTuple[2, Int] = Tuple[Int, Int]
NTuple[3, Int] = Tuple[Int, Int, Int]

Or In general I should be able to write

alias NTuple[N, T] = Tuple[VariadicPack[T, N]]

Then I can dispatch on NTuple[5,Int] instead of Tuple[Int, Int, Int, Int ,Int], it's just shorter.

from mojo.

@JoeLoser while working on this I found a potential issue, StaticIntTuple is imported in builtin/int.mojo which exposes it everywhere as all builtins, is exposing stuff in this way intentional?

from mojo.

@JoeLoser while working on this I found a potential issue, StaticIntTuple is imported in builtin/int.mojo which exposes it everywhere as all builtins, is exposing stuff in this way intentional?

Maybe we should open an issue to have a new mechanism in the stdlib to define what exactly does not need import and what needs imports.

This issue has bitten me quite a few times.

EDIT: Created the issue and proposed a fix that must be implemented partly on the compiler side:

• #2529

from mojo.

Seems like StaticIntTuple is used a lot in the tests, for those cases it should be possible to replace it once Tuple conforms to the Stringable trait

from mojo.

Off-topic: Why _divmod instead of the Python __divmod__?

from mojo.