Repository navigation
Sharpen type annotation of _get_arg_id_to_arg_and_arg_id_to_descr #296
Description
According to the type listed args: tuple[Any, ...], args should be able to support an object type. However, it does not. Passing in an object that is not an pt.Array or scalar or ArrayContainer returns an error message. I think we should just return the descriptor as the position of the object within the args tuple.
Activity
[-]_get_arg_id_to_arg_and_arg_id_to_descr does not support all input arg types[/-][+]Sharpen type annotation of `_get_arg_id_to_arg_and_arg_id_to_descr`[/+]inducer commentedon Jan 16, 2025
First, a point about the
Anytype annotation (https://en.wikipedia.org/wiki/Gradual_typing):Anydoes not mean "you can pass any-and-everything". It represents that no precise information is available, and the type checker should accept any-and-everything.Annotations of
Anyare by their nature stopgaps and should, over time, be replaced by more precise ones. (Here,ArrayOrContainercomes to mind.)For your specific situation, there is currently no support for passing non-(array or container) arguments to
actx.compile'd functions. For correctness, we would have to recompile for each new value, and when we considered it, we did not see many uses cases for that.All that said, what's the use case you have in mind?