deal.II Newsletter #35

[Rene Gassmoeller]

Hello everyone!

This is deal.II newsletter #35.
It automatically reports recently merged features and discussions about the deal.II finite element library.

Below you find a list of recently proposed or merged features:

#6710: Deprecate parallel::distributed::Vector (proposed by masterleinad)
#6709: Remove some more references to astyle (proposed by masterleinad; merged)
#6707: CMake: add a safeguard for accidential /source source directory (proposed by tamiko)
#6706: Update LICENSE file (proposed by tamiko)
#6702: Fix sundials documentation (proposed by Zonni; merged)
#6700: Modify pushed flags for CLANGAUTODEBUG_BUG (proposed by masterleinad)
#6699: Fix warnings in tests (proposed by masterleinad; merged)
#6698: Add clang-format git pre-commit hook (proposed by masterleinad)
#6697: Avoid using unistd.h and sleep (proposed by masterleinad; merged)
#6696: tweak clang-format configuration (proposed by tamiko)
#6695: Generate lapack bindings (proposed by drwells)
#6694: combine CPU and wallclock tables in TimerOutput (proposed by davydden)
#6693: Revert using clang-format in the examples (proposed by masterleinad)
#6692: extend TimerOutput to have dynamic Section width (proposed by davydden; merged)
#6689: Fix multigrid/transfer_04b (proposed by masterleinad; merged)
#6670: Next step in the step-6 introduction. (proposed by bangerth; merged)

And this is a list of recently opened or closed discussions:

#6708 Don't use things like /path/to/dealii in the installation instructions (opened)
#6705 vtable la::p::BlockVector warnings (opened)
#6704 use TableHandler to print TimerOutput (opened)
#6703 Fun with floating point exceptions (opened and closed)
#6701 build issues with Intel 17.0.5 and 18.0.2 (opened and closed)
#6691 TimerOutput class should have dynamic width for Section column (opened and closed)
#6684 Host .tar.gz files ourselves (closed)
#6524 Expand step-6 introduction (closed)
#4883 The new general container type (closed)

A list of all major changes since the last release can be found at this website.

Thanks for being part of the community!

Let us know about questions, problems, bugs or just share your experience by writing to this mailing list, or by opening issues or pull requests on Github.
Additional information can be found at our official website.