meta-typing VS ts-patch

Looks like the arithmetic only supports integers 0 through 10

https://github.com/ronami/meta-typing/blob/master/src/utils/...

A much more practically useful type-level programming in Rust A macro to define type-level logic with value-level syntax in Rust Type-level Brainfuck in Rust "Gentle Intro to Type-level Recursion in Rust" Type-level registers in Rust Type-level quicksort in Scala" Type-level sorting algorithms in Haskell A repo with functions and algorithms implemented purely on types in TypeScript

Here's another repository demonstrating functions and algorithms implemented solely using TypeScript's type system: https://github.com/ronami/meta-typing

yup, just found that, super neat, I am 100% interested in using this for other runtime validation...

It's interesting because I've always been under the impression the TS team was against the use of types at runtime (that's why projects like https://github.com/nonara/ts-patch) exist, but now they're doing it themselves with this project...

I recently learned about Typescript transformers[0] and wish they were better supported in a first-class manner. Working with ttypescript or ts-patch[1] is easy enough, but it still feels like you're doing something you shouldn't be doing.

My goal was to pass the Typescript types to the JS runtime, maybe there's a better way and GPT-4 just led me astray...

[0] https://github.com/itsdouges/typescript-transformer-handbook

[1] https://github.com/nonara/ts-patch

To accomplish this, I wrote a couple of transformer plugins for TypeScript. Now, tsc doesn't support plugins by default. (You may have seen plugins in the tsconfig.json for a project, but they are plugins for the editor's language server, not the compiler.) Luckily for us, again, there exists a fantastic open-source package to solve this problem. Ron S. maintains a package called ts-patch which, aptly, patches the tsc installation for a project to allow the project to specify compiler-plugins.