Design Issue: is `unique_resource` worth it?

[JeffGarland]

After looking at some other libraries like gsl_lite and even the core guidelines, they don't have unique_resource. What is the value of this type of unique_ptr with a deleter? For the file handle case so commonly cited unique_ptr may be used in combination with the c++23 std::out_ptr - this repo for an example from the paper [P1132 out_ptr - a scalable output pointer abstraction] (https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2021/p1132r8.html#design-casting-similar).

So given the existence of P1132 is there any actual rational for this type?

More to discuss here....

[JeffGarland]

Some of the original justification for unique resource is in this paper: https://open-std.org/jtc1/sc22/wg21/docs/papers/2014/n3830.pdf