From b87b31f95c85ac010487313c063a498519ddb46b Mon Sep 17 00:00:00 2001 From: Wolfgang Bangerth Date: Wed, 27 Dec 2023 15:52:53 -0700 Subject: [PATCH] Add a changelog entry. --- .../changes/incompatibilities/20231227Bangerth | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) create mode 100644 doc/news/changes/incompatibilities/20231227Bangerth diff --git a/doc/news/changes/incompatibilities/20231227Bangerth b/doc/news/changes/incompatibilities/20231227Bangerth new file mode 100644 index 0000000000..10eff20d1f --- /dev/null +++ b/doc/news/changes/incompatibilities/20231227Bangerth @@ -0,0 +1,16 @@ +Changed: We have always considered PETSc- and Trilinos-based vectors +that have ghost elements as immutable, i.e., it is possible to read +elements (including the ghost elements) but not to write into them. On +the other hand, the `compress()` function available in all vector +types is meant to communicate values written into non-locally-owned +vector elements to their proper owners, for example during assembly of +a right hand side vector. This `compress()` operation clearly only +makes sense if a vector does not have ghost elements, because only +then is it possible to write into the vector at all, but this +restriction was not enforced -- the `compress()` function simply did +not do anything at all in these cases. This has now changed: Because +it does not make sense to call `compress()` on vectors that have ghost +elements, it is now forbidden to call it and this case will be caught +by an assertion. +
+(Wolfgang Bangerth, 2023/12/27) -- 2.39.5