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

I don't get it. What's wrong with constexpr? It's vastly preferable to macros due to type safety, and const due to compile-time optimization.

  • source
  • hideshow 11 child comments
  • [–] 14 points 1 year ago (10 children)

    I don't get it either. OP might be angry at compile time (Couldn't be worse than rust)

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

    Rust doesn't allow type inference in function signatures, c++ does with auto. IIRC, they recommended against using it, because of -you guessed it- compile time.

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

    Not fair to compare it to the very immature Rust.

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

    I do love rust. But I do like making fun of it too.

    Although I don't see how rust is immature? Unless I missed the joke?

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

    It's very young for a programming language, and is still rapidly evolving.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 2 points 1 year ago

    It's more than 10 years old. It has stable syntax, big standard library, big library ecosystem, plenty of rust programs already in production.

    If by "evolving" you mean "changing", I don't think that is an issue at all. At most, they add features. They don't change or remove. And with the editions system, it should be no issue.

    If by "evolving" you mean "improving", then I don't see how that could ever be an issue.

  • source
  • parent