<html>
<head>
<base href="https://bugs.llvm.org/">
</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 - "Did you mean" suggests deprecated namespaces before non-deprecated ones"
href="https://bugs.llvm.org/show_bug.cgi?id=47928">47928</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>"Did you mean" suggests deprecated namespaces before non-deprecated ones
</td>
</tr>
<tr>
<th>Product</th>
<td>clang
</td>
</tr>
<tr>
<th>Version</th>
<td>trunk
</td>
</tr>
<tr>
<th>Hardware</th>
<td>PC
</td>
</tr>
<tr>
<th>OS</th>
<td>All
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>enhancement
</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>arthur.j.odwyer@gmail.com
</td>
</tr>
<tr>
<th>CC</th>
<td>blitzrakete@gmail.com, dgregor@apple.com, erik.pilkington@gmail.com, llvm-bugs@lists.llvm.org, richard-llvm@metafoo.co.uk
</td>
</tr></table>
<p>
<div>
<pre>// <a href="https://godbolt.org/z/YT1Tra">https://godbolt.org/z/YT1Tra</a>
namespace Views {
int Take();
}
namespace [[deprecated("use Views instead")]] View {
using Views::Take;
}
int main() {
int x = ::Take();
}
<source>:10:13: error: no member named 'Take' in the global namespace; did you
mean 'View::Take'?
int x = ::Take();
^~~~~~
View::Take
<source>:6:18: note: 'View::Take' declared here
using Views::Take;
^
This is reduced from a real piece of code using Range-v3
ranges::view{,s}::take. It seems completely backwards that Clang would suggest
the deprecated synonym (from the using-declaration) rather than the true
version from the non-deprecated namespace.
Perhaps Clang is just thinking that the edit distance between "" and "views" is
longer than the edit distance between "" and "view". However, I think it would
be a nice UX improvement to also consider what kind of entity is being
suggested (is it just a synonym for something from a different namespace? then
follow the symlink) and whether the suggested entity has been explicitly
deprecated (then maybe don't consider it a candidate for suggestion at all).</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>