Or to go all-in - we have a `--strict` flag that gives you `noImplicitAny`, `str... | Hacker News

Hacker Newsnew | past | comments | ask | show | jobs | submit

DanRosenwasser on July 1, 2017 | parent | context | favorite | on: Why We Chose Typescript

Or to go all-in - we have a `--strict` flag that gives you `noImplicitAny`, `strictNullChecks`, `noImplicitThis`, and a mode that always puts you in `"use strict"` mode.

zumu on July 1, 2017 | [–]

I don't understand why `strictNullChecks` is not the default behavior. It being a special compiler option makes me somewhat dubious of TypeScript in general.

Gaelan on July 2, 2017 | | [–]

Backwards compatibility.

Gaelan on July 1, 2017 | [–]

Ah, cool! The last major project I worked on in TS was still before null and this checking.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact