Yea uh is this actually equivalent? In all of those other cases you’re checking if a is null and in the last case my understanding is it is checking to see if a is falsely. In the case that a is 0, or undefined, or an empty array or any other kind of non null falsey value, then the behavior would be different.
Nah this isn’t the way, friend. Instead of adding a bunch of useless anys all over the place, start typing in one part of the application and exclude the rest using a path pattern. Or simply allow .js and only change the extension for files you’ve typed. Doing this is just wasting time and creating false assurances of type safety.
It’s not that hard to define correct, meaningful types. Often vscode already has implicitly determined them for you; just mouseover the variable.
Eh I don’t think being verified means all that much because in my experience there are games that are verified that just don’t play well on a deck because the game doesn’t lend itself well to deck controls and there are others where the control factors keeping them from being verified are trivial but not addressable given valves strict definitions of ‘verified’. Example: Noita sucks on the deck and it’s verified. It’s like 10x more difficult to aim on the deck relative to a M+K setup and makes it feel clumsy as hell. Meanwhile, Against the Storm, Soulstone Survivors, Dwarf Fortress, and Civilization all have great experiences on the deck and I’ve happily played multiple hours of each chilling on my couch without a thought about the controls and none are verified.
Ah interesting one of those cases where this could be one of a few languages. I was reading it as JS.