For example if I had foo(1,2); how does it know if I’m trying to call a function or trying to create an object foo? Is it because the compiler already has seen foo and would just resolve it based on what it knows.
#Function call vs object construction
last steppe
sturdy wharfBOT
lucid prism
noble musk
For example if I had foo(1,2); how does it know if I’m trying to call a function...
depends on the whole line
warm flame
depends on the whole line
As in if it has 'new' before it?
noble musk
not even new is needed
struct X{
int i,j;
X(int i, int j) : i(i), j(j){}
};
int main(){
X x = X(3,4);
return x.i;
}
But yeah either way just avoid such scenarios and you'll be fine. With proper naming it shouldn't happen
warm flame
```cpp
struct X{
int i,j;
X(int i, int j) : i(i), j(j){}
};
int main(){
X ...
Right in this case it's only aware of a type named X and not a top level function of the same name so the resolution is easy
If there's a naming conflict, the compiler might be able to figure it out from context or you'll just get an ambiguity error
Use nouns for types and verbs for functions and you'll be fine
lucid prism
But yeah either way just avoid such scenarios and you'll be fine. With proper na...
There's nothing to avoid here IMO, X x; is a common pattern
left summit
For example if I had foo(1,2); how does it know if I’m trying to call a function...
world war 4 will happen
it'll show an error for u
bc naming conflict