Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
D
dune-common
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Core Modules
dune-common
Commits
1b59d0e0
Commit
1b59d0e0
authored
6 years ago
by
Oliver Sander
Browse files
Options
Downloads
Patches
Plain Diff
Mention Std::variant in the changelog
parent
5237c2c4
No related branches found
Branches containing commit
No related tags found
Tags containing commit
1 merge request
!595
Mention Std::variant in the changelog
Pipeline
#15467
failed
6 years ago
Stage: test
Changes
1
Pipelines
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
CHANGELOG.md
+6
-0
6 additions, 0 deletions
CHANGELOG.md
with
6 additions
and
0 deletions
CHANGELOG.md
+
6
−
0
View file @
1b59d0e0
# Master (will become release 2.7)
-
`dune-common`
now provides an implementation of
`std::variant`
for all compilers
that support C++14. It is contained in the file
`dune/common/std/variant.hh`
,
in the namespace
`Dune::Std::`
. If your compiler does support C++17 the
implementation in
`dune-common`
is automatically disabled, and the official
implementation from the standard library is used instead.
-
When run with an absolute build directory,
`dunecontrol`
now exposes the root build
directory to CMake in the variable
`DUNE_BUILD_DIRECTORY_ROOT_PATH`
.
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment