3 ms·
Arguably, subtyping in am OO language should either be signatures/interfaces only, or you should go full blown multiple inheritance for everything, as with the
by naasking 5y ago
Arguably, subtyping in am OO language should either be signatures/interfaces only, or you should go full blown multiple inheritance for everything, as with the Fortress language.
- klibertp 5y agoIs Fortress the same language that required exponential time constraint solving for its type system?
- naasking 5y agoType checking is not exponential last I checked. However, languages with global type inference have exponential behaviour when inferring types for some pathological programs.
- zaphirplane 5y agoGolang ide struggle with answering what implements this interface. The compiler obviously handles that fine It makes it difficult to jump into an unfamiliar project Assuming that’s what you mean by signature/ interfaces
- cies 5y agoBut this is an issue with tooling. IntelliJ with Java/Kotlin does a great job here.
- zaphirplane 5y agoUnsolved AFAIK, Reducing the ergonomics of the language which is an important point
- jcelerier 5y agoC++ is much more complicated than go in that regards and my IDE generally does not have trouble with it