Re: [Libguestfs] [PATCH libnbd 4/6] lib: Check Closure parameter is not NULL.

The generator has a check that: (* !may_set_error is incompatible with String parameters because * we have to do a NULL-check on those which may return an error. *) Should this check be widened to cover Closure, so that we get a nicer error than 'assert false' if someone goofs in adding a new signature that uses Closure with the wrong return type? Can be a separate patch, since we missed doing it for Enum and Flags in earlier patches, which also are instances where we used 'assert false' and require the ability to return an error. Doesn't affect runtime correctness, just ease-of-use when re-compiling changes to the generator.