mirror of
https://github.com/loot/libloot.git
synced 2026-07-27 14:16:01 -07:00
unique_ptr is simpler, and can be easily converted to shared_ptr if needed, and makes it obvious that each call will return a new pointer. This does mean that if I want to hold onto the objects again in the future for some reason, that'll need the API to change back, but that seems unlikely. unique_ptr not being copyable does make using it a little more awkward, but that only happened in one place in LOOT's code, and there the pointer needs to become shared anyway.