<html>
<head>
<base href="https://llvm.org/bugs/" />
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW " title="NEW --- - Redeclaration inconsistency between struct and int" href="https://urldefense.proofpoint.com/v2/url?u=https-3A__llvm.org_bugs_show-5Fbug.cgi-3Fid-3D24033&d=AwMBaQ&c=8hUWFZcy2Z-Za5rBPlktOQ&r=pF93YEPyB-J_PERP4DUZOJDzFVX5ZQ57vQk33wu0vio&m=-D-VNzmqiLAmK7k6O5fszD1Uyx-nyWCNN9Kkdjbk470&s=xa0FIaMaA72no5nTR2zdMF0Lplod9R9EimVBtjfUESY&e=">24033</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>Redeclaration inconsistency between struct and int
</td>
</tr>
<tr>
<th>Product</th>
<td>clang
</td>
</tr>
<tr>
<th>Version</th>
<td>trunk
</td>
</tr>
<tr>
<th>Hardware</th>
<td>All
</td>
</tr>
<tr>
<th>OS</th>
<td>All
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>normal
</td>
</tr>
<tr>
<th>Priority</th>
<td>P
</td>
</tr>
<tr>
<th>Component</th>
<td>C++
</td>
</tr>
<tr>
<th>Assignee</th>
<td>unassignedclangbugs@nondot.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>anders.granlund.0@gmail.com
</td>
</tr>
<tr>
<th>CC</th>
<td>dgregor@apple.com, llvmbugs@cs.uiuc.edu
</td>
</tr>
<tr>
<th>Classification</th>
<td>Unclassified
</td>
</tr></table>
<p>
<div>
<pre>The following program gives no error when compiling with clang:
namespace X {
struct i {};
}
namespace Y {
using X::i;
struct i {};
}
int main() {}
Let's use int instead of struct, then we get:
namespace X {
int i;
}
namespace Y {
using X::i;
int i;
}
int main() {}
This program gives a redefinition error when compiling with clang.
The only difference between the programs is the kind of entity used (struct or
int), but one compiles without errors and the other gives a redeclaration
error.
Maybe the standard is ambiguous what a redefinition is when it comes to
using-declarations. But shouldn't a compiler make its interpretation
consistently? What is the reason for this inconsistency?</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are on the CC list for the bug.</li>
</ul>
</body>
</html>