New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Triangulation::CellStatus: provide proper compatibility type #15707
Conversation
@pcafrica What about this fix? |
/rebuild |
I wil run this through |
51f01ec
to
f61a802
Compare
The indentation script is unhappy:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK if you can make the documentation work.
This needs a bit more fine-tuning: https://cdash.dealii.org/test/1393689 |
Just create an anonymous |
In addition to the |
@bangerth Yup. On it :-) Update: This cannot work because you cannot implicitly cast between an unsigned int (from an enum) and the enum class. But what works is to provide |
f61a802
to
e866392
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah yes, nice trick. Now these things have the right type too. Well done!
|
||
/** | ||
* @deprecated This is an alias for backward compatibility. Use | ||
* ::dealii::CellStatus directly. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is doxygen able to resolve this even though we delete the dealii namespace?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@tjhei Perhaps not - but then, how am I supposed to tell doxygen to link to the global CellStatus and not the local version?
@tjhei I have merged so that the regression tester can recover. Let's check how the generated documentation looks like and fix if necessary in a follow-up. |
Well done @tamiko! Thanks. |
Great! |
In reference to #15576
In reference to #15698