The gymnastics part is correct. You have to convince the compiler the code you are producing is correct, even if it may be correct already. However, this makes your code way more unlikely to crash or be incorrect.
The "lot of abstractions" is the distinction between type and class the article addresses, I guess?
Comments
The gymnastics part is correct. You have to convince the compiler the code you are producing is correct, even if it may be correct already. However, this makes your code way more unlikely to crash or be incorrect.
The "lot of abstractions" is the distinction between type and class the article addresses, I guess?