1. 26 Jun, 2018 1 commit
  2. 19 Jun, 2018 2 commits
  3. 14 Jun, 2018 2 commits
    • Carsten Gräser's avatar
      Switch default node-to-range-map to HierarchicNodeToRangeMap · 7a17f787
      Carsten Gräser authored
      This is a non-compatible interface change. If you used a range
      on a nontrivial (depth>1) tree, this will not work as before,
      because the range entries are lo nonger accessed using a flat
      index. (But this is very unlikely.)
      
      As long as you only used power<...> or composite<...> in a non-nested
      way, the behaviour should still be the same.
      7a17f787
    • Carsten Gräser's avatar
      Pass treepath to node to range map · db863cea
      Carsten Gräser authored
      In general using the treepath is more natural here.
      While the node stores its treepath this is very likely
      to be removed soon, since in any place where you need
      the treepath it's available by other means (e.g. during
      tree traversal).
      
      Notice that this is an interface change! If you have
      implemented your own node-to-range map, you will have
      to add the additional parameter to operator().
      
      At a later stage one may also want to drop the node argument.
      However, it's not totally clear if this is needed in custom
      maps.
      db863cea
  4. 07 Jun, 2018 1 commit
  5. 03 Jun, 2018 1 commit
  6. 01 May, 2018 1 commit
  7. 27 Apr, 2018 1 commit
  8. 25 Apr, 2018 1 commit
  9. 18 Apr, 2018 1 commit
  10. 17 Apr, 2018 1 commit
  11. 22 Mar, 2018 1 commit
    • Carsten Gräser's avatar
      [cleanup] Get rid of compiler warnings · 417f8be3
      Carsten Gräser authored
      * Remove some unused local typedefs
      * Mark unused values/typedefs in tests by DUNE_UNUSED
      * Use double braces {{ }} in array initialization to
        calm down clang (altough { } is correct here in c++11 and c++14).
      417f8be3
  12. 21 Mar, 2018 1 commit
  13. 07 Mar, 2018 1 commit
    • Carsten Gräser's avatar
      [cleanup] Hide FlatVectorBackend in favour of flatVectorView() · a30be1c8
      Carsten Gräser authored
      * Hide the old implementation class FlatVectorBackend in
        namespace Impl::. It was never documented anyway.
      * Add a new class FlatVectorView. In contrast to the old one,
        this behaves like a (view-) value providing a very slim
        flat-vector-like interface instead of odd static methods.
      * To be flexible FlatVectorView is also hidden in Impl::
        Instead we only expose factory methods:
      * Add factory methods flatVectorView() creating the view
        objects. When passing a const/mutable l-value reference
        the returned object will store a pointer to the underlying
        container. If the passed container is an r-value reference
        the object will be stored by value inside of the view.
        This is necessary to support proxy objects.
      a30be1c8
  14. 27 Sep, 2017 1 commit
  15. 18 Sep, 2017 1 commit
  16. 08 Sep, 2017 1 commit
  17. 07 Sep, 2017 1 commit
    • Carsten Gräser's avatar
      Forbid creation of LocalFunction from temporary · 1871381c
      Carsten Gräser authored
      Since the LocalFunction stores a pointer to the
      DiscreteGlobalBasisFunction, calling localFunction(...)
      with a temporary leads to a dangling reference.
      
      This happens, e.g., when passing a temporary
      DiscreteGlobalBasisFunction to VTKWriter::addVertexData(...)
      because the latter does not store its argument, but
      only the obtained LocalFunction.
      
      Thanks to @max.kahnt for pointing out the issue.
      1871381c
  18. 06 Sep, 2017 4 commits
  19. 10 Nov, 2016 1 commit
  20. 02 Apr, 2016 1 commit
  21. 01 Apr, 2016 2 commits
  22. 31 Mar, 2016 1 commit
  23. 21 Mar, 2016 1 commit
  24. 03 Mar, 2016 2 commits
  25. 22 Feb, 2016 1 commit
    • Dominic Kempf's avatar
      [cmake][bugfix] Correct handling of the EXCLUDE_FROM_ALL property: · f5a42c59
      Dominic Kempf authored
      The signature of `dune_add_test`, that takes the `TARGET` from the user
      produced excluded targets if added in a directory that has the directory
      property `EXCLUDE_FROM_ALL` set. The correct solution IMO is to not use
      that property on test subdirectories anymore (it is a relic from the old
      testing magic), because we rely on `dune_add_test` to handle exclusion.
      
      See core/dune-common#21 for details.
      f5a42c59
  26. 20 Jan, 2016 3 commits
  27. 19 Nov, 2015 2 commits
  28. 17 Nov, 2015 1 commit
  29. 06 Nov, 2015 1 commit
  30. 05 Nov, 2015 1 commit