i’m not sure I can explain my tweet in a single tweet, but the essence is that dependent types depend on some property of object in question
-
-
Replying to @tef_ebooks @buttpraxis
one standard form of dependent typing is being able to handle the notion of a dynamically sized array, carrying length in the type
1 reply 0 retweets 0 likes -
Replying to @tef_ebooks @buttpraxis
having this information in the type, usually implies having this information available at compile time
1 reply 0 retweets 0 likes -
Replying to @tef_ebooks @buttpraxis
‘at compile time’, i mean, some process you can run once, ahead of time, that will always complete yes the halting problem comes in here
1 reply 0 retweets 1 like -
Replying to @tef_ebooks @buttpraxis
anyway, having the length of an array as modelled thing within the types can let a compiler remove length checks or bounds checks
1 reply 0 retweets 0 likes -
Replying to @tef_ebooks @buttpraxis
a similar thing happens in (some) static typed languages: the compiler has enough knowledge that it can omit instructions (for type checks)
1 reply 0 retweets 0 likes -
-
Replying to @tef_ebooks
static type weenies love to pick on dynamic languages, or type checking at runtime the joke is “they are just as guilty of runtime checks”
1 reply 0 retweets 2 likes -
Replying to @tef_ebooks
there’s languages like strongtalk, or erlang, and a few others that show performance or safety doesn’t depend on ahead of time checking
1 reply 0 retweets 1 like -
Replying to @tef_ebooks
so i like to poke fun at static type weenies a lot \o/ and using a more advanced type system to peer down from them like they do at me
3 replies 0 retweets 1 like
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.