Tests aren’t enough: Case study after adding type hints to urllib3

Re:Tests aren’t enough: Case study after adding type hints t... by lamontcg on Monday October 18, 2021 @04:51PM (#28911556)

I'm okay with "var = new FooBarBazThingyWithALongName()" because I don't need to see the type name twice there.

In an IDE you can get the type annotation from the IDE over every inferred var type, but I don't like requiring an IDE to see that information and like it showing up in 'less' as well.

[ Parent | on HN ]

Re:Tests aren’t enough: Case study after adding type hints t... by layer8 on Monday October 18, 2021 @05:02PM (#28911685)

I agree it's redundant if the type name occurs twice in the same statement. However, further evolution of the code often causes the instantiation to be moved elsewhere, and I wouldn't have confidence that the one doing that change then also changes `var` back to the type name. Instead, it would be nice to have syntax avoiding the duplication in the fashion of `FooBarBazThingyWithALongName thingy = new(...constructor parameters...);`.

[ Parent | on HN ]

Re:Tests aren’t enough: Case study after adding type hints t... by Serow225 on Monday October 18, 2021 @06:12PM (#28912483)

C# 9 now has "target-typed new expressions" https://www.thomasclaudiushuber.com/2020/09/08/c-9-0-target-...

[ Parent | on HN ]

Re:Tests aren’t enough: Case study after adding type hints t... by lamontcg on Monday October 18, 2021 @10:16PM (#28914148)

Ideally linting tools on PRs show the refactored code as a violation, and it should be easy to rip a cleanup refactoring across the files before submitting a PR to avoid that.

[ Parent | on HN ]