Made with KolourPaint and screenshots from Kate (with the GitHub theme).

you are viewing a single comment's thread
view the rest of the comments
[–] 14 points 1 year ago (8 children)

It's also valid rust syntax.

But if it were rust, this meme would not make sense, since you would just type let a and type inference would do its thing. Which is much more ergonomic.

  • source
  • parent
  • hideshow 8 child comments
  • [–] 8 points 1 year ago (4 children)

    let a = String::from(“Hello, world!”).into()

    I’ll see myself out.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 4 points 1 year ago (3 children)

    At least be fair and cut out the .into()

  • source
  • parent
  • hideshow 3 child comments
  • [–] 3 points 1 year ago (2 children)

    And bow to the compiler’s whims? I think not!

    This shouldn’t compile, because .into needs the type from the left side and let needs the type from the right side.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 1 year ago (2 children)

    Type inference is a pretty big thing in TypeScript as well though. In fact it's probably the biggest thing about it, IMO.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 1 year ago (1 child)

    I don't know typescript. But if that's the case, this meme doesn't make much sense.

    Who writes the types of variables in a language with type inference unless forced by the compiler?

  • source
  • parent
  • hideshow 1 child comment
  • [–] 1 point 1 year ago

    Maybe it's a language without type interference?

    Either way, it sometimes makes sense in TypeScript to help the type system out a little bit.

    let array: string[] = [];
    

    In this situation, the type system can't infer that the empty array should be a string array, because there are no items to go by.

  • source
  • parent