Ronald S.’s Post

𝗧𝘆𝗽𝗲 𝗪𝗧𝗙 𝗜𝗻𝗳𝗲𝗿𝗲𝗻𝗰𝗲? You know, that “magic” that lets avantgarde-languages like #fsharp or #haskell guess your types without you writing them everywhere — unlike #csharp or #typescript? ——— I’m creating a 𝘃𝗶𝗱𝗲𝗼 𝘀𝗲𝗿𝗶𝗲𝘀 that tears down the mystery and rebuilds it from 𝗳𝗶𝗿𝘀𝘁 𝗽𝗿𝗶𝗻𝗰𝗶𝗽𝗹𝗲𝘀. 𝗧𝗵𝗲 𝗚𝗼𝗮𝗹: Build a language that’s as clean as Python, but as safe as TypeScript by making 𝘁𝘆𝗽𝗲 𝗶𝗻𝗳𝗲𝗿𝗲𝗻𝗰𝗲 the foundation, not an afterthought. ——— 𝗧𝗵𝗶𝘀 𝗳𝗶𝗿𝘀𝘁 𝗲𝗽𝗶𝘀𝗼𝗱𝗲 𝗰𝗼𝘃𝗲𝗿𝘀: • We invent a small expression-based core syntax that's capable for a lot of different text syntaxes • Why type inference isn’t just a “nice feature” you can bolt on later • How to turn typing rules into data structures (constraints) • The three-phase algorithm that powers our type systems • Interactive visualization of the solver at work (see screenshot) ——— No hand-waving. No “it just works.” We’ll walk through the AST, generate constraints from typing rules, and watch the unification algorithm 𝘀𝗼𝗹𝘃𝗲 𝘁𝗵𝗲 𝗽𝘂𝘇𝘇𝗹𝗲 step-by-step. After the video, you’ll understand the theory 𝗮𝗻𝗱 have working code to play with. Where this will go? We'll see :) ——— If you’ve ever been curious about what happens behind the scenes when your IDE shows you type errors before you even run your code — 𝘁𝗵𝗶𝘀 𝗶𝘀 𝗳𝗼𝗿 𝘆𝗼𝘂. 𝗩𝗶𝗱𝗲𝗼 𝗱𝗿𝗼𝗽𝘀 𝘀𝗼𝗼𝗻. Check out my YT channel. #TypeInference #ProgrammingLanguages #CompilerDesign #TypeSystems #SoftwareEngineering

  • graphical user interface, application

To view or add a comment, sign in

Explore content categories