-
Notifications
You must be signed in to change notification settings - Fork 10
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
Feature request: Ability to construct Weak<T>
from RcBorrow<T>
#58
Comments
Yeah, I agree, this is useful. #59 implements the functionality. In retrospect, I wish |
Sorry, I don't have any. It's really a shame that How do you feel about redoing the naming scheme in the next major version (0.2.x)? This would be a breaking change, but the impact of introducing breaking changes tends to accumulate as you try to defer it, which makes it important to iron out any API design issues at the earliest moment possible (this needs to be balanced against annoyance to users, though). I think this is the point of pre-1.0 versions. |
rc-borrow is already v1.0. All of pointer-utils is: it was important to me to signal that these utilities are "production worthy," so I published them at 1.0. On top of this, [ The point is that rc-borrow doesn't need breaking changes, and it won't need breaking changes; the core functionality works as intended and doesn't need API-breaking changes. It'll be sad to lose |
Hmm, I wonder why I thought
Considering the circumstances, this sounds good to me, except that I feel |
I just added I'll consider renaming |
Published as v1.3.0 🎉 |
Currently, one has to first convert
[A]rcBorrow
to[A]rc
before obtainingWeak
. It would be great ifWeak
could be constructed directly without this extra step.The text was updated successfully, but these errors were encountered: