filled() likely already works quite well I think.
empty() should have a type that's more aware of the input value. Right now, it creates a dumb union where empty(string) instead of only applying the "string-related" logic returns a full union where "string could be [], { string: never }, ...".
filled()likely already works quite well I think.empty()should have a type that's more aware of the input value. Right now, it creates a dumb union whereempty(string)instead of only applying the "string-related" logic returns a full union where "string could be [], { string: never }, ...".