• davawen@programming.dev
    link
    fedilink
    English
    arrow-up
    3
    ·
    edit-2
    1 year ago

    ???
    I fail to see the point of this blog post.
    The example given makes no sense (maybe because it’s very simplistic, and a more complicated one would show the point better?), you would NEVER use .iter().count() if you had direct access to the Vec. The iterator is more general in this sense.

    You would use it if, say, your Settings struct was generic over an Iterator type, and in that case it’s the whole point, isn’t it?? Like what???

    Plus, I wouldn’t say this erodes type safety, it’s a lot more like a logic error.

    • armchair_progamer@programming.devOPM
      link
      fedilink
      arrow-up
      1
      ·
      edit-2
      1 year ago

      Yeah this one is kind of a miss on my end. I saw “ad-hoc polymorphism is UNSAFE?” and well, it does a better job reinforcing that ad-hoc polymorphism is not unsafe.

      Author should have wrote a piece “how even type-safe programs can fail” and used his example to show that. Because what this really shows is that type-safety doesn’t prevent programs with the correct types but bad semantics. But that’s not ad-hoc polymorphism; it can happen anywhere (sans ultra-specific types) including even the author’s workaround.