this post was submitted on 26 Oct 2025
8 points (100.0% liked)

Hacker News

2904 readers
471 users here now

Posts from the RSS Feed of HackerNews.

The feed sometimes contains ads and posts that have been removed by the mod team at HN.

founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] xxce2AAb@feddit.dk 3 points 6 days ago (1 children)

It's not obvious to me what you mean, exactly. What do you find confusing about it?

[–] whiwake@sh.itjust.works 2 points 6 days ago* (last edited 6 days ago) (2 children)

I’m saying that when the project gets big, and each of those methods get long, A developer who is new to the project might have some confusion as to why there are methods with the same exact name inside of a class.

[–] xxce2AAb@feddit.dk 3 points 6 days ago

Ah. Since they're targeting host applications written in C or C++, I doubt their target demographic would be unfamiliar with function overloading though.

It's not like one has to use a feature just because it exists, so if it's really an issue just... don't?

[–] Cochise@lemmy.eco.br 1 points 6 days ago (1 children)
[–] whiwake@sh.itjust.works 1 points 6 days ago (1 children)

Yes. Which frequently leads to complications.

#include <iostream>
using namespace std;

void log(int level) {
    cout << "Logging numeric level: " << level << endl;
}

void log(string message) {
    cout << "Logging message: " << message << endl;
}

int main() {
    log('A');  // Uh oh — which one is this?
}
[–] ChairmanMeow@programming.dev 3 points 6 days ago

The level one. But that's more due to implicit casting rather than function overloading imo.