Add Iota operation to direct bindings

[rdspring1]

PR List

• Add threshold and clamp operations to direct_bindings #4876
• Add addcmul operation to direct_bindings #4877
• Add slice operation to direct bindings #4878
• Add Iota operation to direct bindings #4879 << This PR.
• Add full operation to direct bindings #4880
• Add topk operation to direct bindings #4881
• Support alias outputs in direct bindings. #4882
• Add welford operation to direct bindings #4883
• Add scatter operation to direct bindings #4884

[github-actions]

Review updated until commit 3b46dd8

Description

• Added Iota operation to direct Python bindings

• Implemented Python translator handling for IotaOp

• Added test cases for Iota operation functionality

• Updated opinfo metadata to support direct bindings

---

Changes walkthrough 📝

	Relevant files
Enhancement	ops.cpp Add Iota op binding and factory registration                          python/python_direct/ops.cpp Added iota operation binding with parameters (length, start, step, dtype) Added bindTensorFactoryOps function to register new ops Updated bindOperations to include tensor factory ops +33/-1    python_translate.cpp Implement IotaOp translation to Python                                      python/python_direct/python_translate.cpp Added handle implementation for IotaOp translation Set up argument dispatching and default values Generated keyword argument operation for Python frontend +23/-0
Tests	test_python_frontend.py Add test cases for Iota operation                                                tests/python/direct/test_python_frontend.py Added test_iota function with multiple input configurations Verified output correctness against eager mode execution Tested different data types and parameter combinations +23/-0    opinfos.py Update Iota opinfo metadata for direct bindings                    tests/python/opinfo/opinfos.py Added supports_direct_bindings=True to Iota opinfo Updated symbolic parameter list for Iota operation +1/-0

---

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

🧪 PR contains tests

⚡ Recommended focus areas for review Incorrect Step Default The docstring indicates that the step parameter defaults to zero when None, which would produce incorrect or unintended tensor values as a zero step would not increment. This may conflict with the expected behavior of the iota operation. step : Val, optional The step of the tensor. When the default is None, step is set to zero. Potential Null Pointer Handling The code dispatches iop->start() and iop->step() even when they are optional parameters. If these values are null, this could lead to undefined behavior unless the dispatch function explicitly handles null pointers. dispatch(iop->start()); dispatch(iop->step()); Incomplete Test Coverage The added test cases explicitly provide all parameters (length, start, step, dtype). Missing tests for default values (e.g., omitting start or step) may leave edge cases unvalidated. inputs = [ (2, 0, 2, DataType.Int), (3, 100, 1, DataType.Int32), ] def fusion_func(fd: FusionDefinition): for input in inputs: c0 = fd.define_scalar(input[0]) c1 = None if input[1] is None else fd.define_scalar(input[1]) c2 = None if input[2] is None else fd.define_scalar(input[2]) dt = input[3] t3 = fd.ops.iota(c0, c1, c2, dt) fd.add_output(t3)

[rdspring1]

!build

[jjsjann123]

Can we resolve the conflict first? I think this PR is picking up things from #4876

[rdspring1]

@jjsjann123 I rebased this PR.

[jjsjann123]

one nitpick about the python signature of iota.

[rdspring1]

!build