-14
Refusing TypeScript is a signal that you don't care about code quality (vitonsky.net)
submitted 2 years ago by to c/programming@programming.dev
17 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] 2 points 2 years ago (1 child)

Tests are supposed to ensure functionality, not implementation. No useful unit test has ever been made obsolete by a type system. Likewise, if your tests claim your program fulfills its functionality, the type system ads no additional information to the discussion.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 2 years ago (1 child)

    My point was that without a type system you need an impossible 100% code coverage, to be sure that you didn't accidentally mess up some variable assignment or parameter somewhere, since you have nothings to easily and automatically catch those errors.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 2 years ago (1 child)

    I understand your point, I just choose to reject it for the reasons given.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 2 years ago

    I think we are actually saying the same thing though..? Tests should really only ensure functionality. It should be the language's job to help you with obvious implementation errors (such as using a wrong value type).

  • permalink
  • fedilink
  • source
  • parent