Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

15
  • Is asking “why” on language specs still considered as “primary opinion-based” if it can have official answers? Commented Jan 12, 2018 at 16:41
  • Opinion; a view or judgement formed about something, not necessarily based on fact or knowledge. I'm not interested in a view or judgement, and I'd like a factual answer, so I don't think it's an opinion I'm after (as stated). I'd like example scenarios of why this language feature isn't do'able. Commented Jan 12, 2018 at 16:44
  • 3
    What problem are you imagining that this 'feature' would solve? Language designers tend to try to keep languages as simple as possible, so features are not added unless their value is worth the additional complexity, and personally I'm struggling to see the value in this feature. Commented Jan 12, 2018 at 16:54
  • 1
    I'm not certain that anything can't be a language feature. Many things are undesirable as language features, and many other things are not desirable enough to merit the cost of implementing them in a given language Commented Jan 12, 2018 at 17:31
  • 1
    Voting to close for being too broad. There may well be a reason that particular languages don't do this. But, I don't think it'd be accurate to generalize about all OOP languages -- even if we have evidence of this having been an actual decision in the development of any language.... If that makes sense. Commented Jan 14, 2018 at 21:40