▲ | blueflow 8 hours ago | |
I saw the question about weak and strong typing and then realized that i wouldn't know the answer, either. So i looked it up on wikipedia, second sentence there: > However, there is no precise technical definition of what the terms mean and different authors disagree about the implied meaning of the terms and the relative rankings of the "strength" of the type systems of mainstream programming languages. What could have been the right answer? | ||
▲ | Asraelite 4 hours ago | parent | next [-] | |
There's so many other things that are like this too where there is no precise universal definition of the difference but many people think their own personal definition is the correct one: high-level vs. low-level language, functional vs. imperative programming, unit vs. integration test, list vs. array etc. | ||
▲ | wat10000 7 hours ago | parent | prev [-] | |
With a good interviewer, the right answer is anything that indicates you understand the underlying ideas of types and how they work. If someone says “I thought strong typing was when you use it for weightlifting” but they can still describe types being known at compile time versus runtime, type punning, checked versus unchecked conversions, etc., that’s still great. With a bad interviewer, the right answer is whatever specific definition they’ve decided is correct, and if you don’t already know which one that is, too bad. |