Change GaudiConfig2 default semantics to use deepcopy of the default
This merge request changes the GaudiConfig2 DefaultSemantics
so that it makes a deep copy of the default value.
This fixes the problem described in #114 (closed), but if a property with a non trivial type is only modified via its methods, we can only detect changes by comparing the default value with the stored value. Note that we still detect if the property is set to a new value equivalent to the default and handle the case correctly.
Closes #114 (closed)
Merge request reports
Activity
changed milestone to %v36r4
assigned to @clemenci
mentioned in issue #114 (closed)
- Resolved by Marco Clemencic
- Resolved by Marco Clemencic
added 2 commits
added lhcb-gaudi-head label
- [2022-01-08 00:03] Validation started with lhcb-gaudi-head#3130
- [2022-01-08 00:26] Validation started with lhcb-run2-gaudi-head#255
- [2022-01-08 08:14] Validation started with lhcb-gaudi-head#3131
- [2022-01-09 00:03] Validation started with lhcb-gaudi-head#3132
- [2022-01-09 00:09] Validation started with lhcb-run2-gaudi-head#256
Edited by Software for LHCbI checked the ATLAS gaudi-head build that includes this MR and all looks good from our side. I also confirm that it fixes the cases where we saw that default values were being modified accidentally.
mentioned in commit 7fe46a1d