Rewriting TypeScript in Rust? You'D have to be

Re:Rewriting TypeScript in Rust? You'D have to be by Kuinox on Wednesday December 14, 2022 @06:57PM (#33992780)

Code, called implementation here, is a specification written in a certain grammar that is executed.

You want 'evidence' tsc is not working as it should, by writting a duplicated less specifying specification that would sometimes conflict with the typescript one.

It make me remember the people that wanted to specify everything and generate implementation from it: that called a programming language.

[ Parent | on HN ]

Re:Rewriting TypeScript in Rust? You'D have to be by rk06 on Wednesday December 14, 2022 @09:03PM (#33994099)

Code is meant for machine.

Specification is meant for compiler author. Writing one of them is easier than otht

[ Parent | on HN ]

Re:Rewriting TypeScript in Rust? You'D have to be by randomdata on Thursday December 15, 2022 @03:08AM (#33996588)

They are not mutually exclusive. Code identifies a class of language. Specification identifies something that is conveyed through language. Specification can be provided in code.

In fact, while poorly named, what we call testing is actually specification. A test suite specifies for software authors what a program is intended to do and how it is intended to be used. Of course, as a nice side bonus, because the specification is delivered in code the documentation can be validated for truthfulness against an implementation by machine.

[ Parent | on HN ]