-type arguments to class-based
constructors, pass them when calling the task instead.
, for example, is not like the other input parameters to
, which is a
, which must thus be passed in after the
task is initialized with the other parameters. I wonder if there is a way the docs or even the API itself could be tweaked such that the separation between Task and non-Task parameters is somehow clearer or more obvious. Or does that not make sense? e.g. Because parameters can in theory always have either Task or non-Task inputs, depending on how we choose to obtain them. That would make sense. It still makes me wonder if there is a way this could have been done differently so that people don’t have to think about this distinction when initializing tasks. But I will probably understand the current API better as I continue to get familiar with it.