Resource<T> vs Resource<T | undefined>

[yw662]

Isn't every Resource practically a Resource<T | undefined>, since the data needs to be fetched before usable ?
So why not Resource<T> extending from Accessor<T | undefined> instead ? (signal.ts, line 395) ?

[Exelord]

Resource is a generic type. createResource is using <T | undefined> as a generic for Resource which ends with the expected result :)

The Resource type itself has no assumption about async state which allows to use it for multiple purposes respecting the interface.

[cstrnt]

createResource also takes in the initialValue and therefore Resource can in fact be T