Notes on "tuple table" about cython HOT 4 OPEN

Therefore, split tuples into suitable and unsuitable, and use existing code generation for unsuitable.

Don't we do that already with the is_literal and is_partly_literal flags?

from cython.

Don't we do that already with the is_literal and is_partly_literal flags?

Possibly? I think that is_partly_literal is about the multiplication factor.

What I was worried about was if you'd managed to make a tuple that contained another literal initialized at the same time (like slice for example), which would work now because things are processed in order, but not if we did tuples before slices. I'm not sure it's possible to get a slice literal into a tuple though, but I don't know that it isn't.

Either way - it's a detail of a rough outline for later

from cython.

Slices can hold any object whatsoever, obj[(1,2):3, 4] works fine. Though I’ve never heard of that being used for anything, probably better to just bail to regular generated code in those cases. It’d make more sense to do tuples after slices, since array[1:2, 3:4] would be common in Numpy etc code.

from cython.

Yes, you can have tuples with slices and slices with tuples. Difficult to map this to a table then.

from cython.