When Static Typing Meets Code Generation​

Imagine being able to generate JavaScript with the syntax of R and with all the rigor of static typing? This is exactly what JS Blocks enable.

When people first hear about TypR, a very common question comes up:

“Is TypR meant to replace R?”

The short answer is no. The more interesting answer is: TypR is designed to live next to R, not instead of it.

TypR is not a new platform, a new runtime, or a new ecosystem that forces you to rewrite everything. It is a typed language that transpiles to R, and integrates directly into the existing R ecosystem.

Introduction​

Vectorization is one of the greatest tools for data manipulation I know and I am happy that R got this system out of the box. It makes computation simple and simplifies translation from formula to code.

Unfortunately I have encountered one limitation: R's vectors are not very compatible with functional programming or object-oriented programming, two paradigms I like when building libraries or applications. This is what TypR's vectorization is improving with the mechanism of lifting-based vectorization.

After some adventures, the official documentation will soon be open.

Documentation is sometimes hard to maintain because it is an independent entity to the code base. It's even created in a separate github repository.