Use 2.8.0 in dune.module

See merge request !188

Added 2.8 release date

See merge request !187

Merge branch 'changelog-facets-all-all-comm' into 'master'

See merge request !186

Changelog Added entry about All_All communication on facets.

See merge request !185

(cherry picked from commit 985cc2db)

0a228e29 Changelog Added entry about All_All communication on facets.

Merge branch 'issue/fix-warnings-unused-results-printf-format' into 'master'

See merge request !183

Fix some warnings regarding unused results and printf format

See merge request !182

(cherry picked from commit ba0e1089)

8676e9f2 Fix some warnings regarding unused results and printf format
fc299c3a Move variable definition out of the loop

Merge branch 'feature/update-authors' into 'master'

See merge request !181

Oliver Sander authored Jul 16, 2021 and Christoph Grüninger committed Jul 16, 2021

Update list of authors

See merge request !180

(cherry picked from commit c1814445)

5e532337 Update list of authors

Implement the All_All communication interface for facets

See merge request !178

Drop XDR support

See merge request !177

Fix Debug mode

Closes #35

See merge request !160

If I understand it correctly (no documentation in sight), this mechanism
was able to detect whether pointers into the UG3 memory heap were stale,
i.e., did not point to a valid object anymore.  This was used in various
places to verify the data structure integrity. As we have removed the
custom memory heap a long time ago, the HEAPCHECK mechanism cannot be
used anymore (at least to my knowledge you cannot check for pointer
staleness in the system heap).  Nobody noticed this, because the
corresponding assertions were never enabled.  Enabling them leads
to occasional program termination with spurious error messages,
and therefore I herewith remove HEAPFAULT and HEAPCHECK.

HEAPFAULT is some form of consistency check, but I don't really
understand what it is supposed to do.  It may just be a left-over
from the days when UG3 implemented its own memory heap.

The HEAPFAULT in question here triggers an assertion failure
in test-parallel-ug.

It asserts begin < end for a pair of iterators, but the code
right below it handles the cases begin==end, so the assertion
must be wrong.  Nobody notices because apparently nobody ever
enabled the assertion.  Once it is enabled it fires in the
dune-grid standard tests.

The previous way to enable it didn't actually work.

There is an assertion in GetDomainPart that fails when it is actually
enabled.  While this makes it likely that there is a bug somewhere,
the 'part' information is never actually used Dune UGGrid.  I therefore
simply disable the assertion, expecting that this code will be removed
eventually anyway.

Add missing release date for the 2.7.0 release

See merge request !175

... and remove the obsolete comment "unreleased".

Remove support for _2 and _3 macro in dune-grid

See merge request !174

Use [[maybe_unused]] instead of DUNE_UNUSED

See merge request !173

Feature/minor fixes

See merge request !172

Use named struct

See merge request !169

This fixes Clang 11's warning: anonymous non-C-compatible
type given name for linkage purposes by typedef declaration;
add a tag name here [-Wnon-c-typedef-for-linkage]

[ci] Allow failure for Debian 11

See merge request !171

Compiler has an ICE

remove ugdevices from dimension-dependent targets

See merge request staging/dune-uggrid!168

Stabilize ddd type definitions

See merge request !167