Use Hybrid::equal_to instead of Hybrid::equals
From #371 (closed) we get that we want to move to use Hybrid::equal_to
instead of Hybrid::equals
. To give some slack for people to move, we first introduce Hybrid::equal_to
in %DUNE 2.10.0 and later will deprecate .Hybrid::equals
in %DUNE 2.11.0
Closes #371 (closed)
Merge request reports
Activity
changed milestone to %DUNE 2.10.0
requested review from @simon.praetorius
assigned to @santiago.ospina
changed milestone to %DUNE 2.11.0
- Resolved by Santiago Ospina De Los Ríos
@simon.praetorius If this is the way to go I was thinking that we could already introduce
equals_to
in %DUNE 2.10.0, and leave the deprecation ofequals
to %DUNE 2.11.0.
- Resolved by Santiago Ospina De Los Ríos
- Resolved by Santiago Ospina De Los Ríos
changed milestone to %DUNE 2.10.0
added 14 commits
-
195c71c1...3fd176b8 - 13 commits from branch
master
- b66fe020 - Add Hybrid::equal_to in favor of Hybrid::equals
-
195c71c1...3fd176b8 - 13 commits from branch
- Resolved by Santiago Ospina De Los Ríos
I don't think it's to late. For the release we should only consider core and staging, because we cannot control all downstream uses. That's what the deprecation is for. Except for
Dune::Hybrid
itself and its tests in dune-common I can find two uses, one in dune-typetree and one in dune-functions. These should be easy to fix now.