3 ms·
Better question: Why would you want your call site code to break when your type signature gets changed in a way that doesn't necessitate breaking anything?
by cubefox 2y ago
Better question: Why would you want your call site code to break when your type signature gets changed in a way that doesn't necessitate breaking anything?
- yakshaving_jgt 2y agoBecause what you're asking for precludes the concept of mathematical guarantees. I'm not taking your question at face value, because you could be asking why call site code should break when the type signature generalises (which is a useful thing), but that's not what you're asking. It seems you're asking for code to be both null safe and not null safe simultaneously. Having a language just decide that it would like to change the types of the values flowing through a system is wild. It's one of the reasons that JavaScript is a trash fire.
- cubefox 2y agoYou are misunderstanding things.
- yakshaving_jgt 2y agoI’m certainly misunderstanding why so many people in this thread insist on speaking authoritatively on a topic they clearly know very little about.