Re:A 'CSS reset' for TypeScript, improving types for common ...
by dtech on Friday March 03, 2023 @04:46AM
(#35007627)
Such a `dump` function would be 100% the same with unknown, since all types can be converted to top types (both any and unknown in TS)
Re:A 'CSS reset' for TypeScript, improving types for common ...
by badlucklottery on Friday March 03, 2023 @05:19AM
(#35007817)
The difference comes when you interface with other well-typed code and want to convert from any/unknown down to a specific type.
For example:
function handleString(s: string) {
//...
}
declare const a: any;
declare const u: unknown;
handleString(a); // works with zero intervention
handleString(u); // error: Argument of type 'unknown' is not assignable to parameter of type 'string'
handleString(u as string); // works again with explicit re-typing
Re:A 'CSS reset' for TypeScript, improving types for common ...
by capableweb on Friday March 03, 2023 @06:30AM
(#35008217)
A dump function accepting "unknown" is signalling "I'm not sure what this function could handle, probably a lot of different types" vs accepting "any" where it's telling you "I can accept any type you throw at me".
Whereas ‘Unknown’ might be a stepping stone to introduce a more specific type once all the use cases are known. I let it handle strings and integers, log a line about any other type that calls it, and continue behaviour as it is today.