Could you elaborate w.r.t. what you have in mind? Of course dependent types can in principle be used to encode and prove any property; so I guess you mean something more specific?
-
-
What order the tokens go in and how they're spelled.
-
I am also including what the syntax attempts to express and how it is understood by human programmers.
-
Right, that was my expectation.
-
What do you call this extension?
-
The language. ;) Less flippantly, I'd say that I don't think we can draw a line that's concretely about "what people write down" that's separate from the rest of the language design.
-
To take an example, in typed languages, some languages make you write types on the parameters of anonymous functions, others will in general infer them. That's about what you write, but also about lots of fundamental design choices that are not "syntax".
-
All of the following are distinct categories and need better names than "the language" - language semantics that are inaccessible to the language because of missing syntax or other features (accessors and readonly properties in ES3)
-
- syntactic extensions that extend the semantic model but only via syntax (super in ES2015) - aspects of the semantics that compose semantically but not syntactically (concise methods in ES2015 can't be passed to functions) - more I'm forgetting
- 3 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.