Skip to content
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

Consider breaking the naming convention to make types easier to read #11

Open
dtolnay opened this issue Jan 27, 2019 · 0 comments
Open

Comments

@dtolnay
Copy link

dtolnay commented Jan 27, 2019

I find that I am having trouble reading these long types like

struct Struct<T>(PhantomContravariantNeverSendSync<T>);

carefully enough to identify the two important pieces of information contained in them.

Even though it diverges from Rust naming conventions, I think a scheme like

struct Struct<T>(Phantom_Contravariant_NeverSendSync<T>);

would be way easier to read correctly.

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

No branches or pull requests

1 participant