æʃliŋ, purrepurrocessor @aescling@cat.family

@vaporeon_ how comfurtable are you with mathematical purroof—do you know what a purroof by induction is?

@vaporeon_ have you heard of the observation that all logical purroofs are purrograms, and vice versa? the “curry-howard isomorphism”, if you want a fancy name fur it

@vaporeon_ sorry lol

@vaporeon_ yeah sure

@vaporeon_ using some kind of templating ithout needing dynamic rendering

@vaporeon_ somehow there is a wasm compiler fur ocaml, which i’m kinda surpurrised is pawsible, given that ocaml is garbage collected

@vaporeon_ an arguably funnier thing you can do is compile ocaml to js

@vaporeon_ yes

@wallhackio @vaporeon_ yeah var is one of those early design decisions with surpurrisingly frustrating implications fur js implementations because it makes it impawsible to reliably parse in linear time—if you come across what may be an identifier, you do not know until later whether it is actually refurring to something or not

@vaporeon_

// i is in scope HERE!!
for (var i = 0; i < 10; i++) {
    // ...
}
// i is still in scope! 

@vaporeon_ let uses lexical scope. var ignores most blocks aside from function boundaries, and also hoists

@vaporeon_ @wallhackio brother, i wasn’t either, it’s fine lol

@gluedex sbeepy mareepy :3

@wallhackio @vaporeon_ if you look into the semantic diffurences between for with let and var scoped variables, this is not surpurrising; the furmer is surpurrisingly complicated. const allows fur some optimizations over let though iirc

@wallhackio @vaporeon_ that's awful i love it lol

@wallhackio @vaporeon_ oh i can't read, nvm

@wallhackio @vaporeon_ i think you omitted a closing parenthesis?