sh lSSKrSSKJr SSKJr Sr"SS\5rSr Sr S r S r S r S r/S Qrg)N)typeof) as_numba_typec([R"U6$)zProvides an n-dimensional parallel iterator that generates index tuples for each iteration point. Sequentially, pndindex is identical to np.ndindex. )npndindexargss f/Users/tiagomarins/Projetos/claudeai/copy_bank/venv/lib/python3.13/site-packages/numba/misc/special.pypndindexr s ::t c\rSrSrSrSrSrg)prangezProvides a 1D parallel iterator that generates a sequence of integers. In non-parallel contexts, prange is identical to range. c[U6$N)range)clsr s r __new__prange.__new__s d|r N)__name__ __module__ __qualname____firstlineno____doc__r__static_attributes__rr r rrs r rcSSKn[X 5nSRUVs/sHnSPM sn5U-nSU<SU<S3n0n[X`U0U5 UR US5$s snf)Nr,z"%s"zdef _gdb_func_injection(): (z) _gdb_func_injection)numbagetattrjoinexecnjit) func_namer r!fn_argstrdefnls r _gdb_python_call_genr,sl  "B XXt,t!vt, - 4F f D A2" ::a-. // -s A$c&[S/UQ76"5 g)z Calling this function will invoke gdb and attach it to the current process at the call site. Arguments are strings in the gdb command language syntax which will be executed by gdb once initialisation has occurred. gdbNr,rs r r.r.#s &&(r c$[S5"5 g)a Calling this function will inject a breakpoint at the call site that is recognised by both `gdb` and `gdb_init`, this is to allow breaking at multiple points. gdb will stop in the user defined code just after the frame employed by the breakpoint returns. gdb_breakpointNr/rr r r1r1,s)*,r c&[S/UQ76"5 g)a Calling this function will invoke gdb and attach it to the current process at the call site, then continue executing the process under gdb's control. Arguments are strings in the gdb command language syntax which will be executed by gdb once initialisation has occurred. gdb_initNr/rs r r3r36s+d+-r cU$)aForces Numba to interpret *obj* as an Literal value. *obj* must be either a literal or an argument of the caller function, where the argument must be bound to a literal. The literal requirement propagates up the call stack. This function is intercepted by the compiler to alter the compilation behavior to wrap the corresponding function parameters as ``Literal``. It has **no effect** outside of nopython-mode (interpreter, and objectmode). The current implementation detects literal arguments in two ways: 1. Scans for uses of ``literally`` via a compiler pass. 2. ``literally`` is overloaded to raise ``numba.errors.ForceLiteralArg`` to signal the dispatcher to treat the corresponding parameter differently. This mode is to support indirect use (via a function call). The execution semantic of this function is equivalent to an identity function. See :ghfile:`numba/tests/test_literal_dispatch.py` for examples. r)objs r literallyr6@s . Jr cU$rr) containers r literal_unrollr9Zs r ) rrrr r.r1r3r6r9)numpyrnumba.core.typing.typeofrnumba.core.typing.asnumbatyperr objectrr,r.r1r3r6r9__all__rr r r?sD+7V 0)-.4 r