Types, Objects and Generic Types
Tags: CompilersAssume the axiom that punctuation is evil. Using multiple kinds of brackets for similar functionality in a language is unnecessarily complex.
The result is:
The relationship between a generic type and it’s concrete types should be expressed in the same way as for the relationship between a type and the objects that are instances of it.
In C++, constructors use: foo(object1, object2), but templates use Foo<Baz,Bar>
Can we unify the syntax for these similar concepts without making the language complex?
It’s completely clear to me why using different punctuation makes it easier to explain how the compiler is implemented, and easier to implement the compiler. But I don’t think the distinction is necessary to make the source code easier to read and write.
Let’s say we only have “objects”. “Type” would be a role that on object plays with respect to another object. The compiler simply instantiates some objects at compile time, as part of the compilation process. That seems like a clear concept for coders to understand.
The goal of a programming language is to facilitate the writing and maintaining of software. It’s not to make the compiler’s job easier.