Skip to content

struct Foo(); shouldn't be parsed as struct Foo; #15095

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
ben0x539 opened this issue Jun 22, 2014 · 0 comments · Fixed by #15098
Closed

struct Foo(); shouldn't be parsed as struct Foo; #15095

ben0x539 opened this issue Jun 22, 2014 · 0 comments · Fixed by #15098

Comments

@ben0x539
Copy link
Contributor

Looks like struct Foo(); is accepted and makes an expression Foo a value of that type, just like the regular form struct Foo; does. Since Foo() as an expression still doesn't work, this is kinda confusing, and anyway not intended as far as I know.
@ben0x539 ben0x539 mentioned this issue Jun 22, 2014
Merged
bors added a commit that referenced this issue Jun 23, 2014
@bors
auto merge of #15098 : ben0x539/rust/nullary-tuple-struct, r=pcwalton
baa7208 
Reject `struct Foo();` to fix #15095.
bors added a commit to rust-lang-ci/rust that referenced this issue Jul 17, 2023
@bors
Auto merge of rust-lang#15095 - davidlattimore:lib-workspace-deps, r=…
7ebe7ac 
…lnicola

Change in-tree libs to workspace dependencies and bump versions
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

Successfully merging a pull request may close this issue.

libsyntax: don't allow enum structs with no fields ben0x539/rust
1 participant
@ben0x539