`pick`, `omit`, `require` & `partial` should use arrays instead of objects

I was wondering what the rationale behind pick, omit, require and partial expecting objects is?

Each value is optional and can only be true, so using

.pick(['foo', 'bar'])

feels more sensible than

.pick({ foo: true, bar: true })

There is another reason than convenience:
Currently you can (accidentally) add properties, which do not exist on the original object.
With an array you could ensure type safety.

The signature would look like this

pick<Mask extends Array<keyof T>>(mask: Mask): ZodObject<Pick<T, Extract<keyof T, keyof Mask>>, UnknownKeys, Catchall>;

If you agree I could offer to implement this. Either in a backwards compatible way (also accepting objects, using overloads) or as a breaking change.

[colinhacks]

This syntax is already implementable without const, that’s not the problem. It’s just a footgun that will cause users frustration. This is the part that makes this syntax a footgun, and const doesn’t fix that unfortunately.

[colinhacks]

Too much of a footgun. Many many people will inevitably try this:

const keys = ['a', 'b'];

const schema = z.object({
  a: z.string(),
  b: z.string(),
  c: z.string()
}).pick(keys); // bad

Which is bad because Zod can’t properly type the resulting schema, since the type signature of keys has collapsed to string[].

A similar problem exists for z.enum and it’s caused a lot of headaches both for users and maintainers.