Concore C++ class is resource-owning but implicitly copyable (Rule-of-Five violation)

[avinxshKD]

concore.hpp owns shared-memory handles/pointers and has destructor cleanup, but copy/move semantics are not explicitly defined. That allows accidental shallow copies of ownership state, which is unsafe and can lead to duplicate cleanup paths. Expected is explicit ownership model (non-copyable + safe moves / RAII wrapper). Current behavior is fragile and easy to misuse.

Expected, clear ownership semantics for resource-owning type:
delete copy ctor/assignment
implement safe move ctor/assignment (or equivalent RAII wrapper object)

[avinxshKD]

Hey @pradeeban @Rahuljagwani what do you think of this? plan is to delete copy ops, implement move ctor/assignment with proper SHM handle transfer, and wrap the cleanup logic in a small RAII type.