Mistakes with Rust smart pointers: when Deref goes wrong

Re:Mistakes with Rust smart pointers: when Deref goes wrong by tragomaskhalos on Monday July 10, 2023 @02:39PM (#36671024)

I worked on a C++ codebase where there was a method had two overloads - one with 36 char* arguments, and one with 37. Obviously one hardly knows where to begin pointing out the problems. I'd like to report that it was some sort of elaborate joke, but honestly not sure. I think Rust, as in so many areas, made the right call here.

[ Parent | on HN ]

Re:Mistakes with Rust smart pointers: when Deref goes wrong by Animats on Monday July 10, 2023 @04:23PM (#36672421)

I'm currently trying to figure out who calls this C++ method in a large code base:

    bool operator()(const LLDispatcher* dispatcher, const std::string& key
    ...

Yes, they actually overloaded "()".

[ Parent | on HN ]

Re:Mistakes with Rust smart pointers: when Deref goes wrong by qsdf38100 on Monday July 10, 2023 @08:03PM (#36674802)

I don't follow. How does this declaration overloads "()"?

[ Parent | on HN ]