subject:"\[Issue 4699\] Functions in peer scopes cannot have the same name"

[Issue 4699] Functions in peer scopes cannot have the same name

2019-08-18 Thread d-bugmail--- via Digitalmars-d-bugs

https://issues.dlang.org/show_bug.cgi?id=4699 Simen Kjaeraas changed: What|Removed |Added CC||issues.dl...@jmdavisprog.co

[Issue 4699] Functions in peer scopes cannot have the same name

2015-06-09 Thread via Digitalmars-d-bugs

https://issues.dlang.org/show_bug.cgi?id=4699 Andrei Alexandrescu changed: What|Removed |Added Version|D1 & D2 |D2 --

[Issue 4699] Functions in peer scopes cannot have the same name

2014-03-18 Thread d-bugmail

https://d.puremagic.com/issues/show_bug.cgi?id=4699 Infiltrator changed: What|Removed |Added CC||lt.infiltra...@gmail.com --- Comment #1

[Issue 4699] Functions in peer scopes cannot have the same name

2014-03-19 Thread d-bugmail

https://d.puremagic.com/issues/show_bug.cgi?id=4699 Infiltrator changed: What|Removed |Added CC||bearophile_h...@eml.cc --- Comment #2 f

[Issue 4699] Functions in peer scopes cannot have the same name

2014-03-29 Thread d-bugmail

https://d.puremagic.com/issues/show_bug.cgi?id=4699 --- Comment #3 from Stewart Gordon 2014-03-29 12:21:31 PDT --- Because the two functions named f0 are in disjoint scopes, the compiler shouldn't care about the fact that they have the same name. I can see a problem in that at the moment the m

[Issue 4699] Functions in peer scopes cannot have the same name

2014-03-29 Thread d-bugmail

https://d.puremagic.com/issues/show_bug.cgi?id=4699 --- Comment #4 from bearophile_h...@eml.cc 2014-03-29 12:25:35 PDT --- (In reply to comment #3) > So this is presumably a temporary restriction in the > compiler pending a name mangling scheme that avoids this. Walter could answer if this rest