Borrow-checking without type-checking

(scattered-thoughts.net)

42 points | by jamii 3 hours ago

1 comments

  • Panzerschrek 1 hour ago
    In my programming language I have some sort of "borrowing" too (although it's named differently). But my language has no dynamic typing, only static typing is used and thus all checks are compile-time and have no runtime cost. Why bothering with dynamic typing and paying runtime costs for it?
    • jamii 1 hour ago
      > The goal is that most of your code can have the assurances of static typing, but you can still opt in to dynamically-typed glue code to handle repls, live code reloading, runtime code generation, malleable software etc.
    • Pay08 43 minutes ago
      Dynamic typing is neat, I actually prefer it to static typing. Most people who think they have a problem with dynamic typing actually have a problem with weak typing.
      • choeger 41 minutes ago
        Dynamic typing is no typing.

        The point of types is to prove the absence of errors. Dynamic typing just has these errors well-structured and early, but they're still errors.

      • antonvs 40 minutes ago
        Technically, in a type theory context, there’s no such thing as “dynamic typing”. Types are a static, syntactic property of programs.

        The correct term for languages that don’t have syntactic types is “untyped”.

        > Most people who think they have a problem with dynamic typing actually have a problem with weak typing.

        All people who say things like this have never studied computer science.

      • teaearlgraycold 40 minutes ago
        Yes to dynamic typing. Yes to static analysis.