epam / epam/Indigo

Explicitly disable move operations for Pools

Open
#849 0 comments 0 reactions 1 assignee Claimed by @AStepaniuk View on GitHub
c++ Core
Dominant language
C++
Stars
406
Forks
134
Avg merge
2d 11h
Merged PRs (30d)
24

Description

**Problem description**
Currently classes `Pool`, `ObjPool`, `PtrPool` are already non-movable due to implicitly disabled move constructors/assignment operators.
I think it is fine to have move operations disabled for those classes, because Pools are often referenced by multiple objects. So, if such pool will be moved - all the external references will become dangling.
It is safer to keep move operations disabled.

So, the idea of this issue is make this disable to be explicit.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.