Markus Blatt
Markus Blatt
I could not see any sign why the move constructor should make the object invalid in all situation. We only make sure that `elements.begin==elements.end` holds but maybe do not make...
You are right in this regard. of course. I failed to see that.
If that were a compiler bug it should have happened to many code. Maybe some out of bounds writing. I will try to get access to a matching porter box...
To me the problem might not be in opm-common. I tested this on Debian's platti porter machine. If I add a simple unrelated print statement (`std::cout
jenkins build this ignore_extra please
jenkins build this ignore_extra please
Cool, finally this works with all existing tests, see [jenkins #6985](https://ci.opm-project.org/job/opm-common-PR-builder/6985/). The two difference to the previous attempt are: - I had to move a few methods to delay instantiation...
I still would like to rerun my local tests for this. Sorry that this takes so long. Somehow things keep popping up...
I cleared the milestone. This is just too delayed.
jenkins build this ignore_extra please