Sjmarf@sh.itjust.works to Programmer Humor@programming.dev · 1 year ago“It’s not that hard”sh.itjust.worksimagemessage-square39fedilinkarrow-up19arrow-down10
arrow-up19arrow-down1image“It’s not that hard”sh.itjust.worksSjmarf@sh.itjust.works to Programmer Humor@programming.dev · 1 year agomessage-square39fedilink
minus-squareThorry84@feddit.nllinkfedilinkarrow-up0·1 year agoYes the compiler/interpreter can figure it out on the fly, that’s what we mean by untyped languages. And as stated both have their merits and their faults. Elon doesn’t know what the words mean and just chimes in with his AI future BS.
minus-squarejanAkali@lemmy.onelinkfedilinkEnglisharrow-up0·edit-21 year ago Yes the compiler/interpreter can figure it out on the fly, that’s what we mean by untyped languages. Are there untyped languages? You probably meant ‘dynamically typed languages’. But even statically typed languages can figure out most types for you from the context - it’s called ‘type inference’.
minus-squarenul@programming.devlinkfedilinkarrow-up1·1 year agoMost of my code is untyped. First I type it, then I realize it’s all wrong and use backspace to untype it.
Yes the compiler/interpreter can figure it out on the fly, that’s what we mean by untyped languages. And as stated both have their merits and their faults.
Elon doesn’t know what the words mean and just chimes in with his AI future BS.
Are there untyped languages? You probably meant ‘dynamically typed languages’.
But even statically typed languages can figure out most types for you from the context - it’s called ‘type inference’.
Most of my code is untyped. First I type it, then I realize it’s all wrong and use backspace to untype it.