I swear there's a lot of software engineering "best practices" out there that result from people talking themselves into believing that necessary workarounds weren't anti-patterns of a language's quirks but rather features of it.
Alas, recent comments suggest it is *the* pattern to use :(
-
-
i mean, don't check at all; just iterate it and if the caller gave you garbage it's their problem
-
eh, not always a really practical approach
-
but more practical than a lot of people expect
-
for sure. It's just that for a lot of data sci stuff it can be irritating
-
I'm curious, can you give me an example so I can understand your use case better?
-
Ah, sure... implementig algorithms where things go from vector-like to scalar-like
-
What I really want is the type inference to be a little bit smarter and let me do smthing like foreach x in v:.... and have it be fine *without* having to write code around it, for style reasons more than anything
-
hm, i'm still not sure i entirely follow (possibly too general), but that's ok
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.