With works happening both internally (ex: our codegen) and externally (ex: numba-cuda), it has become clear that yaml files like this (from numba-cuda) are better than json ones because
- it allows comments
- it avoids weird syntax errors (ex: no comma in the last line)
Let's just unify our infrastructure and always use yaml instead of json. The only drawback that I am aware of is that GHA does not provide a built-in fromYAML function (whereas there is fromJSON), but I am sure we can work it around.
With works happening both internally (ex: our codegen) and externally (ex: numba-cuda), it has become clear that yaml files like this (from numba-cuda) are better than json ones because
Let's just unify our infrastructure and always use yaml instead of json. The only drawback that I am aware of is that GHA does not provide a built-in
fromYAMLfunction (whereas there isfromJSON), but I am sure we can work it around.