"warning: explicit link request could not be resolved" - but I didn't explicitly request a link

[eyalroz]

Describe the bug
I have the following doxygen comment for some method of mine:

/**
 * @brief Create a variant of ::std::unique_pointer for an array in
 * device-global memory.
 * 
 * @tparam T  an array type; _not_ the type of individual elements
 *
 * @param device on which to construct the array of elements
 * @param num_elements the number of elements to allocate
 * @return an ::std::unique_ptr pointing to the constructed T array
  * 
 */

And for every translation unit which includes this header, doxygen gives me:

/path/to/header.hpp:26: warning: explicit link request to 'std::unique_pointer' could not be resolved

I didn't make an explicit link request!

Also strange is that I don't get the same warning about the second appearance of std::unique_ptr.

To Reproduce
Just make sure that comment above is stuck onto a a relevant function.

Expected behavior
No warning. Either there's auto-linkification (which there might be) or there isn't.

Version
1.11.0 (42d0f98*)

[albert-github]

Doxygen recognizes that :: ... is something that can be linked and does some automatic linking.

Based on the information provided I got with the ::std::unique_pointer and the ::std::unique_ptr a warning:

.../header.hpp:5: warning: explicit link request to 'std::unique_pointer' could not be resolved
.../header.hpp:12: warning: explicit link request to 'std::unique_ptr' could not be resolved

so:

• Can you please attach a, small, self contained example (source+configuration file in a, compressed, tar or zip file!) that allows us to reproduce the problem? Please don't add external links as they might not be persistent (also references to GitHub repositories are considered non persistent).

[eyalroz]

@albert-github : Here you go:

10713.zip

Notes:

• The doxygen.cfg is an auto-generated one with no manual changes.
• The reason I use the initial :: is because NVIDIA uses a namespace cuda::std, and I use namespace cuda, so I have to differentiate by using "fully-qualified" namespaces.

[eyalroz]

@albert-github : I don't know what the reminder frequency is on this issue tracker... so, ping about the example you requested.

[albert-github]

I don't see a neat solution for this problem only workaround I can see is to use ::%std::unique_ptr
Maybe @doxygen has an idea

[doxygen]

@albert-github I think the warning is simply not correct in this case.

@eyalroz Please verify if the referenced commit fixes the problem for you. Do not close the issue, this will be done automatically when the next official release becomes available.

[eyalroz]

@doxygen Verified.

By the way, how do you automate the closing of issues by making releases?

[doxygen]

This issue was previously marked 'fixed but not released',
which means it should be fixed in doxygen version 1.11.0.
Please verify if this is indeed the case. Reopen the
issue if you think it is not fixed and please include any additional information
that you think can be relevant (preferably in the form of a self-contained example).