Skip to content
This repository has been archived by the owner on Apr 8, 2024. It is now read-only.

Handle ambiguous type with bounds? #50

Open
ehuss opened this issue Jun 28, 2019 · 0 comments
Open

Handle ambiguous type with bounds? #50

ehuss opened this issue Jun 28, 2019 · 0 comments
Labels
ambiguity Potential sources of ambiguity grammar Issues with the definition of the rust grammar

Comments

@ehuss
Copy link
Contributor

ehuss commented Jun 28, 2019

libsyntax rejects certain type positions to not include bounds. That is, the following are rejected syntactically:

Where Example
Cast expression x as dyn A + B
Raw pointer type *const dyn A + B
Bare function return type fn() -> dyn A + B
Reference type &dyn A + B

Should this be encoded in the grammar?
@ehuss ehuss added the grammar Issues with the definition of the rust grammar label Jun 28, 2019
@eddyb eddyb added the ambiguity Potential sources of ambiguity label Jul 1, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
ambiguity Potential sources of ambiguity grammar Issues with the definition of the rust grammar
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ehuss @eddyb