That usually motivates me to solve my problem.
type MergedType = TypeA & TypeB9.9/10 cases there is a design flaw happening here, I and others I work with have found this to be true. We have zero // @ts-ignore statements in a very large code base that dozens of developers work with every day.
Using interface extensions properly helps tremendously here
Probably a good rule of thumb is that you get to use a ts-ignore if you can link it back to an open issue on the TS repo :)
That said, I haven't run into this in my many years of working with TypeScript except once.
There are legit cases for `any` where it doesn't detract any type safety at all but the number of people that understand them is very small (fully convinced 99% of TypeScript devs doesn't even know most of the things in the official docs).
Then for a few seconds I remember the names behind Typescript's design, its type system capabilities, and a possible excuse to use C++ via addons, and it kind of lightens my day.
This is a very impressive project in my view - it's baffling that you would have the wherewithal to link the discussion you did but not realize the novelty here.
In addition to type-level analogues of your normal Lodash-esque functions, it includes a suite of type-level parser combinator utilities and is built on higher-kinded type abstractions.
Can you run your whole payroll app at compile time via TypeScript types too?
HN thread on this here: https://news.ycombinator.com/item?id=43184291
Everytime i hear Ocaml has a complex type system i refer them to Typescript.
tmcanada•6mo ago
https://github.com/sinclairzx81/typebox#syntax
cjonas•6mo ago
qbane•6mo ago