jitify | A single-header C++ library for simplifying the use of CUDA Runtime Compilation (NVRTC) | GPU library

Well, first of all, we did say it's a sequence (ex: list/tuple) of strings and gave an example in the doc page you quoted:

name_expressions (sequence of str) – A sequence (e.g. list) of strings referring to the names of C++ global/template kernels. For example, name_expressions=['func1', 'func1', 'func2'] for the template kernel func1 and non-template kernel func2. Strings in this tuple must then be passed, one at a time, to get_function() to retrieve the corresponding kernel.

So I don't see any ambiguity. There is no doubt that it's such a common pitfall in Python to write ('abc') and thinking it's a 1-element tuple containing the string 'abc', for which it should been written as ('abc',) with comma. But checking for such pitfall everywhere in the codebase would be a pain in the ass IMHO.

Second, even if we add a check to ensure the input is iterable, it still doesn't solve your issue as strings are also iterable/sequence: