tyrade VS typic

But there's no law of nature that says that Rust type-level syntax must suck forever. Maybe Rust 2036 will make writing this stuff a breeze, who knows. But for now, there are some projects that attempt to fill this gap, like Tyrade, which is a Rust DSL (like, a proc macro) that compiles down to bare Rust. It has seen some usage: there's a session types library built on top of Tyrade that is just awesome:

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

However, if I were starting over, I think I would take the approach of /u/entoros's tyrade project.

https://github.com/willcrichton/tyrade#more-complex-example-session-and-list-types

Seconding this! This is the approach I took while developing typic, a library that models Rust's repr(C) layout algorithm at a type-level. I would first sketch out my ideas in prolog, then translate that Prolog fairly mechanically to trait impls. I even started automating this translation. (The tricky bit is that you really need to strictly limit yourself to a subset of prolog, and maintain a fairly rigid style discipline, too.)

I'd like to try to rewrite typic with tyrade, but I'd need to first swap out tyrade's peano-arithmetic number system for typenum's binary-arithmetic system.