Skip to content

newtype structs and tuple structs should have (or just allow) priv fields #5489

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
thestinger opened this issue Mar 22, 2013 · 2 comments
Closed

newtype structs and tuple structs should have (or just allow) priv fields #5489

thestinger opened this issue Mar 22, 2013 · 2 comments

Comments

@thestinger
Copy link
Contributor

At the moment a newtype struct can just be constructed and used as the original type with a dereference outside of the module. It's not possible to use them as an independent new type.
@thestinger thestinger reopened this Mar 22, 2013
@alexcrichton
Copy link
Member

Nominating for feature-complete

@graydon
Copy link
Contributor

graydon commented May 23, 2013

closing INVALID, we don't have privacy on tuples; make a field name if you want privacy

@graydon graydon closed this as completed May 23, 2013
@sfackler sfackler mentioned this issue Oct 1, 2013
Closed
oli-obk pushed a commit to oli-obk/rust that referenced this issue May 2, 2020
@bors
Auto merge of rust-lang#5489 - phansch:node-id-hir-id, r=flip1995
e5fe56d 
Cleanup: `node_id` -> `hir_id`

This removes some more `node_id` terminology from Clippy and replaces one occurrence of `as_local_node_id` with `as_local_hir_id`, which should be doing the same for that particular case.

changelog: none
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
3 participants
@graydon @alexcrichton @thestinger