• mormegil@programming.dev
    link
    fedilink
    arrow-up
    0
    ·
    14 days ago

    Tells you exactly what and at which line the problem is?

    Syntax error: unmatched thing in thing from std::nonstd::__map<_Cyrillic, _$$$dollars>const basic_string<epic_mystery,mongoose_traits<char>, __default_alloc_<casual_Fridays = maybe>>

    • Ephera@lemmy.ml
      link
      fedilink
      arrow-up
      0
      ·
      14 days ago

      I was going to respond with “Segmentation fault”. Truly a classic.

      (Yes, that’s not a compile error, but well, it should be.)

      • palordrolap@kbin.run
        link
        fedilink
        arrow-up
        0
        ·
        14 days ago

        Well, it is theoretically possible for code to cause a compiler to segfault. As for how, well that’s a different matter. You’ll need deep knowledge of the compiler, or else the assuredness that it can’t possibly happen. Because then it will.

      • RustyNova@lemmy.world
        link
        fedilink
        arrow-up
        0
        ·
        14 days ago

        Well until you are deep into trait/future/generic territory. Because then you’ll go in big fuck (full type being in a separate file) not being correct somewhere in this shit.

        Don’t get me wrong, I love rust. But those area really need some love

        • 5C5C5C@programming.dev
          link
          fedilink
          arrow-up
          0
          ·
          14 days ago

          Still much better than C++ templates, and I say that as someone who used to genuinely love C++ template metaprogramming. Admittedly Rust traits+generics are far more limited than C++ templates, but very often I find that to be a positive. The list of things that I feel traits+generics are missing is small and rapidly shrinking.