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

Rc #1

Open
Tamschi opened this issue Oct 13, 2021 · 0 comments
Open

Rc #1

Tamschi opened this issue Oct 13, 2021 · 0 comments
Labels
domain: Rust Involves Rust code. good first issue Good for newcomers Hacktoberfest A good-for-Hacktoberfest issue. This label is only maintained in October. priority: someday If you need this, please let me know! state: approved Approved to proceed. type: feature Brand new functionality, features, pages, workflows, endpoints, etc. work: clear A known solution is (to be) implemented.

Comments

@Tamschi
Copy link
Owner

Tamschi commented Oct 13, 2021

Is your feature request related to a problem? Please describe.

The current implementation is generic enough to support !Sync reference-counting for all consumers, too.

Describe the solution you'd like

Adapt sync::Arc into an rc::Rc struct.
The API should be extremely similar, but decrements and acquires should be relaxed.

Describe alternatives you've considered

None.

Additional context

There are opportunities for fallible (TryFrom) conversions between these types and Box.
Remember to .acquire() when moving away from either Arc or Rc!

@Tamschi Tamschi added type: feature Brand new functionality, features, pages, workflows, endpoints, etc. good first issue Good for newcomers priority: someday If you need this, please let me know! state: approved Approved to proceed. work: clear A known solution is (to be) implemented. Hacktoberfest A good-for-Hacktoberfest issue. This label is only maintained in October. domain: Rust Involves Rust code. labels Oct 13, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
domain: Rust Involves Rust code. good first issue Good for newcomers Hacktoberfest A good-for-Hacktoberfest issue. This label is only maintained in October. priority: someday If you need this, please let me know! state: approved Approved to proceed. type: feature Brand new functionality, features, pages, workflows, endpoints, etc. work: clear A known solution is (to be) implemented.
Projects
None yet
Development

No branches or pull requests

1 participant