Skip to content

Remove *Box suffix from smart pointers. #6651

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.

Sign up for GitHub

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

Jump to bottom
Closed
brson opened this issue May 21, 2013 · 2 comments
Closed

Remove *Box suffix from smart pointers. #6651

brson opened this issue May 21, 2013 · 2 comments

Comments

@brson
Copy link
Contributor

brson commented May 21, 2013

Seems redundant. Rc, RcMut, Gc, GcMut, AtomicRc, UnsafeAtomicRc are a good set of smart pointers. Are there others?
@brson brson mentioned this issue May 21, 2013
Closed
@brson
Copy link
Contributor Author

brson commented Aug 12, 2013

It's actually only UnsafeAtomicRcBox that has this problem. I misunderstood how the others were designed when I named it.

@emberian
Copy link
Member

emberian commented Jan 6, 2014

No longer an issue.

@emberian emberian closed this as completed Jan 6, 2014
Jarcho pushed a commit to Jarcho/rust that referenced this issue Aug 29, 2022
@bors
Auto merge of rust-lang#9269 - nahuakang:collapsible_str_replace, r=f…
5820add 
…lip1995

Lint `collapsible_str_replace`

fixes rust-lang#6651

```
changelog: [`collapsible_str_replace`]: create new lint `collapsible_str_replace`
```

If you added a new lint, here's a checklist for things that will be
checked during review or continuous integration.

- \[x] Followed [lint naming conventions][lint_naming]
- \[x] Added passing UI tests (including committed `.stderr` file)
- \[x] `cargo test` passes locally
- \[ ] Executed `cargo dev update_lints`
- \[x] Added lint documentation
- \[x] Run `cargo dev fmt`
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@brson @emberian