Hi! I’ve created this page to showcase the features of Mint (since there are so many) and their corresponding versions in other similar languages.

  • Caveman@lemmy.world
    161·
    2 days ago

    TS as a statically typed language is not what I would call it. It’s a language with enforced type annotations but can be circumvented pretty easily. For example when receiving a JSON from an http request a string field can be just whatever.

    • FizzyOrange@programming.dev
      71·
      2 days ago

      That’s nitpicking. It is statically typed. Is Dart not statically typed because it has dynamic.

      You could call it “gradually typed” if you want to be pedantic.

      can be circumvented pretty easily

      That means it isn’t sound.

      • Caveman@lemmy.world
        5·
        2 days ago

        Gradually typed is a great description because it’s neither fully static or dynamic. TS does allow you to circumvent the types too easily to be called statically typed.

        const strings: string[] = ([1] as any[])

        Is ok in TS land so the type of strings is not really static so to speak because you can assign whatever to it. Writing this in Dart would give

        error - The argument type 'List<dynamic>' can't be assigned to the parameter type 'List<string>'. - argument_type_not_assignable

        if I’m not mistaken.

        • hikaru755@lemmy.world
          3·
          1 day ago

          I get your point, but that’s not a great example. Kotlin is a statically typed language, and this compiles (and runs!) just fine:

          val test: List<String> = listOf(1) as List<String>
println(test) // prints "[1]"

          Even val test: String = 1 as String will compile, but at least gives you an exception at runtime, which the equivalent typescript wouldn’t.

            • hikaru755@lemmy.world
              2·
              1 day ago

              Unfortunately not. You do get a warning that it’s an unchecked cast at least.

              Granted, the issue here is generic type erasure, which was a tradeoff that was decided on for backwards compatibility when generics were first introduced to Java, so it’s not like an actually desirable feature of the language. But the point is that this wouldn’t be reason for anyone to not call Java and Kotlin not statically typed, their type system is just a bit weaker than others in certain aspects