• tias@discuss.tchncs.de
      link
      fedilink
      arrow-up
      11
      ·
      edit-2
      5 months ago

      I think the article makes a good point, but perhaps I’m over-interpreting. It’s not that we should stop using strings. It’s that we should use the type system to separate different kinds of strings and enlist the compiler’s help to detect incorrect mingling of them. So for example a symbol type would only permit strings that contain ASCII letters, underscore and digits, and concatenation with / conversion to plain strings would be limited.

      • Kogasa@programming.dev
        link
        fedilink
        arrow-up
        2
        ·
        5 months ago

        The analytic continuation of KB(x) to the complex plane subject to a superconvexivity constraint is unique but doesn’t necessarily have a straightforward geometric interpretation

    • chickenf622@sh.itjust.works
      link
      fedilink
      arrow-up
      3
      ·
      5 months ago

      It’s definitely a rule that can be taken so far that it is counterproductive, but I think it’s good practice to thbk about how I could use something other than a raw string ( even if it’s just a constant defined somewhere )

    • corytheboyd@kbin.social
      link
      fedilink
      arrow-up
      1
      ·
      edit-2
      5 months ago

      You joke, but Rails actually does make Integer do too many things lol. I’d argue they’re useful things, but it does so by patching the core Ruby Integer class :p