-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
Why does save-analysis use it's own syntax? #57136
Comments
fn local_waker<W>(wake: Arc<W>) -> LocalWaker it's valid generic function, cc https://doc.rust-lang.org/reference/items/functions.html#generic-functions |
I know, but the function name |
@jendrikw oops, I misunderstood your comments, sorry. |
Triage: a long time later, save-analysis is eventually on the way out, and so this might just be moot. |
Save-analysis has been removed from the compiler. |
In the save-analysis file of liballoc, the value/signature of
rust/src/liballoc/task.rs
Line 98 in 14b9665
fn <W> (wake: Arc<W>) -> LocalWaker
, which is not valid rust code.There is little documentation available for the save-analysis, but as far as I understood it, the
value
field is supposed to represent the signature. In most other languages, the signature of a function doesn't include the parameter names.For consistency, I think it would be better if the field would either include the function name or leave of the parameter names.
Edit: I want this to be able to parse the string with syn, which expects either a name for the function or no names for the arguments.
The text was updated successfully, but these errors were encountered: