Skip to content

rust manual: supertraits seperator is wrong #14465

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

Merged
merged 1 commit into from
May 29, 2014
Merged

Conversation

Ryman
Copy link
Contributor

@Ryman Ryman commented May 27, 2014

No description provided.

@bors bors closed this May 29, 2014
@bors bors merged commit ada85a2 into rust-lang:master May 29, 2014
bors added a commit to rust-lang-ci/rust that referenced this pull request Jun 5, 2023
Limited syntax support for return type notations (RTN)

Experimental RTN bound support was recently merged into rustc (rust-lang#109417), the goal of this PR is to allow experimentation without syntax errors everywhere.

The parsing implemented currently aligns with the state of the tracking issue, it only supports the form `T<foo(..): Bounds>`. The parser always checks for the presence of `..` to disambiguate from `Fn*()` types, this is not ideal but I didn't want to spend too much time as it is an experimental feature.
bors added a commit to rust-lang-ci/rust that referenced this pull request Jun 5, 2023
…=Veykril

Parse associated return type bounds

This PR implements parser support for associated return type bounds: `T: Foo<bar(): Send>`. This PR does not implement associated return types (`T::bar(): Send`) because it's not implemented even in rustc, and also removes `(..)`-style return type notation because it has been removed in rust-lang#110203 (effectively reverting rust-lang#14465).

I don't plan to proactively follow this unstable feature unless an RFC is accepted and my main motivation here is to remove no-longer-valid syntax `(..)` from our parser, nevertheless adding minimal parser support so anyone interested (as can be seen in rust-lang#14465) can experiment it without rust-analyzer's syntax errors.
flip1995 pushed a commit to flip1995/rust that referenced this pull request Apr 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants