Incorrect atom type inference when setSelf is destructured and write function args are typed.

[dmaskasky]

Bug Description

Not sure yet, but it looks like the read function is being taken as the value in the case where setSelf is destructured and write args are typed.

const derived = atom(
  (_get, { setSelf }) => 'string',
  (_get, _set, arg: string) => {},
)
const store = createStore()
const v = store.get(derived2)

// ------------ Types Inferred ------------

const derived: WritableAtom<(_get: Getter, { setSelf }: {
    readonly signal: AbortSignal;
    readonly setSelf: SetAtom<unknown[], unknown>;
}) => string, string[], void> & WithInitialValue<(_get: Getter, { setSelf }: {
    readonly signal: AbortSignal;
    readonly setSelf: SetAtom<unknown[], unknown>;
}) => string>

const v: (_get: Getter, { setSelf }: {
    readonly signal: AbortSignal;
    readonly setSelf: SetAtom<unknown[], unknown>;
}) => string

Reproduction Link

https://www.typescriptlang.org/play/?#code/MYewdgzgLgBAJgUwE4EsBuC4wLwwIZQgC2AFAFAwwkD6A5glADQwDeMEDAyggDYBmMAL4BKHAD4YAcmiowtSYwpU6DZtQ5N8SWgC52UWbVHYJLQYuFkyoSLGggkCHDGCOCCToUclLN6DDRne0cAOnooEkRUDDhLMgB6eJgAWlS09IzMrOyc3OyrPgBXMGAoFHAXNygPLwQfPU8HJxYlSkcoQqQwVkF8CBhGxzJBKygATwAHJwBBMDGANTweQqdcYoBrMBAAdzAycamYWbHpwiJnU+IAHmPF5YQxUcmnQdXWJXC9K7uVsRICYh6S5Eb5LX7GCQ-BBKDRfKHMabafoIAAe1TAcH6Gy2uwA2gBdZgAJQQEEKPCgf1a+DOegA6qgoHgAEY8BDA0H3BFI4mk8mUxSUSghEV4JFApFKCEwElkikwwrMvT-WlHObA5g8FDQBBgZDK6VoEAoWLiKiG41wYZPQ4AcQY1SQzk5vxVgKOZxdD2lUJtLwdyGd8KOSJgqPRmJg2J2YAJvLllPIlABRHpjJZbI5wcRtAg8f5YkFMBFITFuYlubI0tl-L9AwYHJzyLRusj0bxhJlfIpElwNzDLYx-SbVOFovFRyrZpr8v2zy7eDgXuY3Cg3H4zj1GCQvaoHwYentUEdRZAEzK4AgehaQpgbjg4B4Y3YKFoYCWQOZDjXr-fPGp8QAFSAdSMCAewXC8AI2owHwDgwCgYCOn+UYcDAj7PngGLsIqABWCClDAhAuAAFlh9AwNsKBQCRICFLAWxlMACAhKB4EAAKIBMjjAO4WAAKpoTRThECgKKIZR1Ekau64CPRKBauMsFIMQMC4SATIoPE8k8P0iE6oubHxNS94YRBa5QQ0kH8Eo5hTiYMC+nOhwMtRCA3KG4atliYCbDGcZdgmu5JjAnwwEeJ4wge9bHsgRYlmWV4hpW1bdlAViJDAAAqJEwTBWEIUhyAoQcThYVgjEwBMYqwCAAgTIqWrAEcAAKACSrGZQAIiAMCVVxrbod01F9AhsC8d0wBkXIThUTRdEMRpKDMaxpUwHSUltWA1EoEsUJeruN6FdRei+iMzlOAA8mA-FgEQdFIc4PhmkaJp1tdACyD1QB5uYDhGPl+R2+Y9s6SicP93kxY2PKBQWiijuZwINBYZrXbd93FLAAA+ASWlYqITN+hWOnweDMR61xQqYSiEJ4hgGmaMiIbQSj3noJKLgdSjFNAGYINQ2oAPz-ECnrtmAYjCHoX4gGyWFKIgzKFLQAAyLK8ELejM3IShASBQrgVlvWXQAcqrACaMDMk4hQcFgzLPgAUhpeAoDAWrMkgYooKSRG9UQYrrDSxD9Hg-Tceg7ghAMeEEbAxFTeRLGtBxkdoO4qfGZQSsqy10TuFr1sgHLCAK5Q+upzAABiKCOGHfCOiH5wwY4fDILqzEO8+wn6E0sHwb3fB1-4ZRENChvZblen9NACk8Pg3SE8gKDj0hSytW1i9YGSzL4YRifTRRc20fRfVLStWc87Y-PUOAW3UUXJDBAgDS1Bab3nYTxOIaT5NOK5JkrJ2SemzJ5QcbZfI4ljJ2GclIlBeSHJTEE1N3htDLnADmGDlzQ09E2EGlJHiUG2IyV+61SG-TzHDHsShwBfSxkXT631KEEMeOdNaMkmTVGmKUcoYADrOChDAXGJASDcQQGgU6YIEA+mkXEb+SAE7znzqvHaGAszSN3IA-mHIlDwiULiTh7geEXn4dTQkShXpWkeGQNksB1gIDGAAYW+s4AADDATKtAeAgGZBvBxz5QBYwHk6JYC8UwQAykkEh1F+bwBXjEZuZAFGwCKCUUxzccFNkhkgiWAU4GI3ZguJcwZVww1zKwwsSgYnVDTG5Fh1CBRVjqUAzMoDpHcgqY0mxmV7zJDMlEdAmAkkpNgsUXhFQUwHRIEUzmJTNHS2QdzBI0TSH9LAE+eJ0RhkpmSSiImiixnpL4ZksBf1EGQKBjA1hIVEI7T2tIqRXJqmkJae5fB3SLAtJ0e0rkyUqEFJgAAMnWptbaZQHn3GWZlSOokygYGbpJeaZ87kQoXhne4eyDmpPGRkqZ1N6gwBUXCoZGj7jCKjBiBAw89RwAkECpQG0aIPzRftIRuNiiIBpZgHpSRYVqLKmcLFxM0kTO6PizRtzwW7R4FCJ5KwvlEtQCS9RvzfjAtBcy6VkKVjLNGaKvFaqECdObADSlVz8lpUKRgou7Lik4LKXg2GBSqnENIUXQB7znVWtRkdPw9jHHOAAAYpgACQsAANQRoCS4rGggg1KH9S4cAw9aDOCOpQOmBgWbPQzUKdonRug0W1CEXOasNb-lvLeIWMAAkwAjVIHQkh61EWnqWhAyty020rVWygegAnUjspQXo4dyGxOAWShV-zWEarYKi210iKWcupYhYZIxKAoAECQUqdU7wYJwNgXAkgDV8MkKIPNNhU0hHvM4G9o65kOobE6rpLrbJhl0s0akl7XwhFRbejBX6U0-pvbgLleB+RzMA2AK9NS3hgf5J60aEtRqeoaQU2yShN1UFg+eqDMHSHOFgxh9BHQujJug6+a0ZAT0VHgxSB9BLi1JUnQ8ZgYUIrIFwyRwtoUGDbunpYc6NHuh0agKhgltNp56GJQKljrreNQEPAGJARZYQxUismbQVk1xcPZGKg6vq2YMB4xoEKmbp5Fkzc8XdZYD1HuE5IUCMAa3-G0KNMRjhJGOTkWaKEwgSDhH49qYQlhe16DLEWQTZAgA

[dai-shi]

As I understand, setSelf cannot be typed correctly, or it's too tricky. It's an internal tool, so we are probably happy to make it unknown. (And, I would like to drop setSelf entirely eventually.)

[Wendystraite]

Weird, my first thought was that TypeScript overloads were not working correctly, but just duplicating the first overload solved the problem.

I also fixed it using type inference instead of overloads, but it's uglier.

See this sandbox. I added inside a lot of expectTypeOf (from expect-type) inside to play with it.