Duplicate query names produces cryptic Go error

[CaptainCharlieGreen]

If you accidentally create two queries with the same name the generated go code has an error about an 'ambiguous selector"

-- name: GetReportByID :one
SELECT * FROM abuse_report
WHERE id = $1;

-- name: GetReportByID :one
SELECT * FROM abuse_report
WHERE id = $1;

Produces in db.go:

	if q.getReportByIDStmt, err = db.PrepareContext(ctx, getReportByID); err != nil {
		return nil, fmt.Errorf("error preparing query GetReportByID: %w", err)
	}
	if q.getReportByIDStmt, err = db.PrepareContext(ctx, getReportByID); err != nil {
		return nil, fmt.Errorf("error preparing query GetReportByID: %w", err)
	}

which fails to compile:
"ambiguous selector q.getReportByIDStmt"

My expected behavior is sqlc fails generation with an error indicating there are multiple queries with the same name.

[CaptainCharlieGreen]

I can try my hand at a PR for this if you'd like.

[kyleconroy]

My expected behavior is sqlc fails generation with an error indicating there are multiple queries with the same name.

That's the behavior I'd expect too.

I can try my hand at a PR for this if you'd like.

I think I have a good idea on how to fix it. Let me take a pass first.

[kyleconroy]

@CaptainCharlieGreen this should now be fixed in the latest version of sqlc.