You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For some reason Doxygen seems to make a difference between structs/classes and concepts when it comes to name lookup for link generation.
In the following snippet for example Doxygen is able to create a link to the plain struct but not the concept.
namespacec {
/// \page LinkConcept/// Link to NoConcept works, but link to Concept does not!structNoConcept {};
template<typename T>
concept Concept = requires(T a) {
{ std::hash<T>{}(a) } -> std::convertible_to<std::size_t>;
};
} // namespace c
The only way I found to get this to work is to explicitly link it using the complete path \ref c:Concept
I'm currently on version 1.9.8. For convenience, here's the main.cpp containing the code and the doxyfile: doxygen_concepts_issue.zip
The text was updated successfully, but these errors were encountered:
@higaski Please verify if the referenced commit fixes the problem for you. Do not close this issue, this will be done automatically when the next official release is made available.
This issue was previously marked 'fixed but not released',
which means it should be fixed in doxygen version 1.10.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).
For some reason Doxygen seems to make a difference between structs/classes and concepts when it comes to name lookup for link generation.
In the following snippet for example Doxygen is able to create a link to the plain struct but not the concept.
The only way I found to get this to work is to explicitly link it using the complete path
\ref c:Concept
I'm currently on version 1.9.8. For convenience, here's the main.cpp containing the code and the doxyfile:
doxygen_concepts_issue.zip
The text was updated successfully, but these errors were encountered: