I think as stated, the third reason needs some extra steps to fit naturally into "why dynamic typing" and that it contains two separate things, which is that
when a type system is expressive/easy-to-use enough, it can actually help human programmers to be explicit about types. it's not just about helping the compiler emit efficient code.
but still sometimes it's nice to be able to avoid being explicit about types, especially during early stages of code development (?)
I have a hard time thinking about whether 2 is specific to dynamic type systems. Does the auto keyword in C++ count as a way to sort of "not hear about types"?
https://github.com/JeffBezanson/phdthesis/blob/def06095b6d211329974e8919bb5519c1b904a7d/chap1.tex#L309
I think as stated, the third reason needs some extra steps to fit naturally into "why dynamic typing" and that it contains two separate things, which is that
I have a hard time thinking about whether 2 is specific to dynamic type systems. Does the
autokeyword in C++ count as a way to sort of "not hear about types"?