This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug go/49889] New: Calling a function whose name is obscured by a local variable does not produce an error
- From: "rluble at gmail dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Thu, 28 Jul 2011 18:35:56 +0000
- Subject: [Bug go/49889] New: Calling a function whose name is obscured by a local variable does not produce an error
- Auto-submitted: auto-generated
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49889
Summary: Calling a function whose name is obscured by a local
variable does not produce an error
Product: gcc
Version: 4.7.0
Status: UNCONFIRMED
Severity: minor
Priority: P3
Component: go
AssignedTo: ian@airs.com
ReportedBy: rluble@gmail.com
Created attachment 24859
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=24859
Small program exhibiting the mentioned error
When calling a function whose name is obscured by a local variable on a *tuple
assignment* statement (as in the example below) no error is produced and the
generated code does not have the function call.
func test(a int) (int, int) {
b:=a+1
return b,a
}
func main() {
test, a := 1, 1
c,d := 1,1
c,d = test(a)
}
The expected behaviour is to produce an error.