Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Put operation should return a shared_ptr to the object, otherwise a copy is always needed #34

Closed
aliaksei-imi opened this issue Jan 15, 2025 · 2 comments

Comments

@aliaksei-imi
Copy link

Almost always cache check/put operations are followed by returning results to the callee, e.g.

auto val = std::shared_ptr{nullptr};

const auto [cached_val, cached_ok] = cache.TryGet(key);

if (!cached_ok) {
  # for example, val is already a shared_ptr
  val = Calc(key);
  cache.Put(key, val);
  return val;
}

return cached_val;

so current implentation doesn't allow storing shared_ptr, only shared_ptr<shared_ptr>.

Otherwise we must always copy the object to the cache because Put doesn't return a shared_ptr for newly created smart pointer, if it did, we could have done

const auto [cached_val, cached_ok] = cache.TryGet(key);

auto val = SomeType{};

if (!cached_ok) {
  val = Calc(key);
  auto val_shared_ptr = cache.Put(key, std::move(val));
  return val_shared_ptr;
}

return cached_val;
@aliaksei-imi
Copy link
Author

aliaksei-imi commented Jan 15, 2025

although, looking again at the code, even with a move in the latter case, Insert will anyways initiate a copy constructor, which does not seem right for large objects

@aliaksei-imi
Copy link
Author

reopened in #35

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant