Is the “not nullable” attribute meaningful for G (S)Lists?

[Max Reeves <reeves max 2 gmail com>]

As the empty G(S)List is represented by NULL, this makes it a perfectly valid G(S)List. For most other objects NULL represents the absence of an object. I suppose it's possible to have NULL represent both the empty list and the absence of an object, eg a NULL G(S)List argument to a "nullable" in parameter could just be ignored - as it probably would anyway. But what sense does it make to mark a G(S)List parameter or return value as "not nullable"?

I'm currently working on a binding from libraries with GIR data to Standard ML, so I'm concerned what approach I should use to pass “not nullable” G(S)List or if I should completely ignore it. Are there any introspectable code conventions I should know about that regulates this?

Thanks,

Max