include_directories already has custom type coercion (see ther
`coerce_dirs()` call), so it should probably be left as obj_any.
I suppose link with could be more strict (obj_build_target), but I'm
Thanks for this! Overall, I think (hope) we can be a little more strict
with some of these. Basically using obj_any means that we have to write
some sort of custom type checking logic, so to the extent possible we
should let interp_args handle it. Perhaps the meaning of
ARG_TYPE_ARRAY_OF is a little unclear; `ARG_TYPE_ARRAY_OF | obj_string`
for instance means this:
'hello' # gets coerced to ['hello']
['hello', 'there', false]
So it can provide even more type checking than plain old obj_array did.
I have made a few suggestions, but maybe I am to optimistic. My plan so
far has been to implement the strictest possible checking, and slowly
loosen it until an acceptable portion of meson projects can be built