3 ms·
Why on earth? It is resolved by the compiler, there is absolutely no performance difference between using var and explicitly specifying the type.
by tigershark 9y ago
Why on earth? It is resolved by the compiler, there is absolutely no performance difference between using var and explicitly specifying the type.
- ambulancechaser 9y agoundoubtedly that person was talking about LINQ and not var usage
- JustSomeNobody 9y agoYes, LINQ not var.
- btschaegg 9y agoWell, that on the other hand does indeed make sense, depending on the context. The only question there could be if it's a good idea to use a garbage collected language to directly[1] interact with hardware. [1]: Well, at least directly enough for LINQ performance to be a problem.
- JustSomeNobody 9y agoWe're not real time, but we do have some time constraints. Yes, all this was kicked around and argued about.
- dbattaglia 9y agoOr possibly confusing "var" and "dynamic"?
- tigershark 9y agoUndoubtedly he didn't read properly then. The banned feature was var, linq was just heavily frowned upon.