Skip to content

default specialization keyword not supported for associated constants #4264

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
aloucks opened this issue May 2, 2020 · 1 comment
Closed

default specialization keyword not supported for associated constants #4264

aloucks opened this issue May 2, 2020 · 1 comment

Comments

@aloucks
Copy link
Contributor

aloucks commented May 2, 2020

The following compiles on nightly with specialization enabled, but rust-analyzer flags the default keyword as an error.

#![cfg(feature(min_specialization)]
#![cfg(feature(specialization)]

trait Foo {
    const BAR: i32;
}

impl Foo for () {
    default const BAR: i32 = 1;
}

Related:

#1402
#1415
This was referenced Jun 3, 2020
Closed
Merged
bors bot added a commit that referenced this issue Jun 4, 2020
@bors @Avi-D-coder
Merge #4737
e66c7b3 
4737: Parse default unsafe & default const r=matklad a=Avi-D-coder

Closes: #4718 #4264

Co-authored-by: Avi Dessauer <[email protected]>
@matklad
Copy link
Member

matklad commented Jul 15, 2020

fixed some time ago

@matklad matklad closed this as completed Jul 15, 2020
@blefevre blefevre mentioned this issue Aug 7, 2020
Closed
lnicola pushed a commit to lnicola/rust-analyzer that referenced this issue May 20, 2025
@RalfJung
Merge pull request rust-lang#4264 from RalfJung/rustup
311ef02 
Rustup
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
@aloucks @matklad