Document exactness of constructions in Epick #7412
Conversation
|
/build:v0 |
|
/build:v0 |
|
/build:v1 |
|
There was an error while building the doc: |
lrineau
added
the
rm: not for next release
|
/build:v2 |
1 similar comment
|
/build:v2 |
|
The documentation is built. It will be available, after a few minutes, here: https://cgal.github.io/7412/v2/Manual/index.html |
|
Looks like you have to add the |
sloriot
added
Batch_2
sloriot
added
Under Testing
and removed
rm: not for next release
|
Successfully tested in CGAL-6.0-Ic-116 |
lrineau
added
the
rm only: ready for master
lrineau
removed
the
rm only: ready for master
|
Hi @HoffmannMichael, this work you did during last CGAL developers meeting is eventually merged in the documentation. |
|
Thx, Laurent,
I saw it and I’m delighted. :-)
Cheers, Michael
… On 30 Nov 2023, at 10:00, Laurent Rineau ***@***.***> wrote:
Hi @HoffmannMichael, this work you did during last CGAL developers meeting is eventually merged in the documentation.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.
|
|
Luckily you had come to the previous developer meeting. Hope to see you in Lyon :> |
Summary of Changes
Document which constructions are always guaranteed to be exact for
Epick. These are mostly access functions and/or sign changes. But as the representation of geometric objects is not specified, the user has no way to know. Documenting which constructions are exact allows to reason about the correctness of user code using epic and some of these "trivial" constructions.It is implemented by putting a list on the doc page of
Epickitself and also add an "Exactness" comment on the page of the corresponding member or global function.Release Management