- Mar 05, 2020
-
-
Christoph Grüninger authored
-
- Jan 21, 2020
-
-
Ansgar Burchardt authored
Several members of `std::allocator` were already deprecated in C++17 and have now been removed in C++20. This patch uses the appropriate members of `std::allocator_traits` instead.
-
- Apr 10, 2019
-
-
Carsten Gräser authored
Replace many `Hybrid::ifElse(IsNumber<...` constructions by using `Impl::asMatrix()`. In some cases the (now only) implementation of the matrix branch was additionally cleaned up using range-based for.
-
- Dec 03, 2018
-
-
Oliver Sander authored
-
Oliver Sander authored
Feel free to put the test back in if it does serve a purpose that I missed. But please, if you do so please add an explanation.
-
- May 16, 2018
-
-
Jö Fahlke authored
Stop doing memory management ourselves, use a `std::vector` instead. This has the advantage that allocation, deallocation, construction and destruction of elements is handled for us using the supplied allocator in an exception-safe manner. This has the disadvantage of using an extra pointer and an extra size_type in `base_array_unmanaged`, which are kept syncronized with the `std::vector` used as storage. Anything else would require interface modification of `base_array_unmanaged` and `block_vector_unmanaged`, which in turn would require modifications to `BlockVectorWindow`, `MatrixBase`, and `VariableBlockVector` and make this patch even larger. This adds a `swap()` operation and move-construction/assignment to `BlockVector`. The one-argument versions of `resize()` and `reserve()` now behave exactly as they do for `std::vector`. This means that using `reserve()` to shrink the capacity of a BlockVector no longer has any effect. Apart from that, the behaviour with regard to capacity on copy and move has also changed to that of `std::vector`: copying will only expand the capacity of the copied-to vector to accomodate the size of the copied-from vector, not necessarily it's capacity. This deprecates the two-argument versions of `resize()` and `reserve()`, and makes them behave exactly the same as the one-argument versions, ignoring the second argument. The second argument specified whether or not to copy the old values upon reallocation. This conflicted with the common container semantics of always copying/moving. For `resize()`, it also conflicted with the common signature where the second argument specifies the value for newly created elements. There were only two uses of the two-argument version of `resize()` in dune-istl that triggered in the unit tests (both in arpackpp.hh), and those had no effect different from the the one-argument version, because the BlockVectors were empty before the `resize()`. Fixes: #41 Requires: - dune-common!494 for the tested allocators to be usable with `std::vector`.
-
Jö Fahlke authored
-
Jö Fahlke authored
-
Jö Fahlke authored
-
- Apr 05, 2017
-
-
Christian Engwer authored
-
- Oct 25, 2016
-
-
Carsten Gräser authored
These constructors and assignments are all implemented using a downcast to derived class and may lead to undefined behaviour. This commit removes the checks for these methods in preparation for their removal.
-
- Feb 18, 2016
-
-
Oliver Sander authored
So far, each dune-istl vector class had its own unit test. They all tested, among other things, for compliance with the dune-istl vector interface. This lead, or had the risk to lead, to subtle differences between the individual tests. Also, since there is no formal specification of the interface, it was somewhat unclear what the interface actually requires. This patch tries to improve the situation by providing a generic set of tests that should be passed by anything claiming to be a dune-istl vector. This will save work, because it allows to centralize tests that are now distributed across the different unit tests for the different dune-istl vectors. Also, it is my hope that these centralized tests can serve as some form of formalized specification of the dune-istl vector interface.
-
Oliver Sander authored
Integers do not form a field, hence 'int' is not a sensible field_type.
-
- Feb 17, 2016
-
-
Oliver Sander authored
-
- Nov 25, 2015
-
-
Elias Pipping authored
-
- Jul 13, 2015
-
-
Oliver Sander authored
-
- Nov 28, 2013
-
-
Christoph Grüninger authored
-
- Aug 15, 2013
-
-
Christian Engwer authored
add blockvector test for nested block vectors
-
- Aug 13, 2013
-
-
Markus Blatt authored
-
- Jul 09, 2013
-
-
modify constructor with capacity to catch at least some of the wrong invocations (see doxygen comment).
-
- Jul 04, 2013
-
-
Christian Engwer authored
modify constructor with capacity to catch at least some of the wrong invocations (see doxygen comment).
-
- Oct 05, 2012
-
-
Christian Engwer authored
[[Imported from SVN: r1725]]
-
- Jun 08, 2012
-
-
Christian Engwer authored
[[Imported from SVN: r1623]]
-
Christian Engwer authored
[[Imported from SVN: r1622]]
-
- Oct 13, 2009
-
-
Christian Engwer authored
* update configure and Makefiles [[Imported from SVN: r1100]]
-
- Nov 05, 2008
-
-
Markus Blatt authored
[[Imported from SVN: r956]]
-
- Jul 10, 2008
-
-
Markus Blatt authored
Test for implicit size constructor. [[Imported from SVN: r914]]
-
- Nov 25, 2006
-
-
Markus Blatt authored
[[Imported from SVN: r698]]
-
- Aug 22, 2006
-
-
Markus Blatt authored
[[Imported from SVN: r650]]
-
- Oct 07, 2005
-
-
Markus Blatt authored
[[Imported from SVN: r346]]
-
Markus Blatt authored
[[Imported from SVN: r341]]
-
- Oct 05, 2005
-
-
Markus Blatt authored
[[Imported from SVN: r336]]
-