Skip to content

/api-guidelines

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

Add guidance about when and how to create open enums #113

Open
brson opened this Issue Jul 24, 2017 · 1 comment

Comments

Assignees
No one assigned
Labels
new guideline
Projects
None yet
Milestone
No milestone
3 participants
@brson @sfackler @dtolnay
@brson
Copy link
Contributor

brson commented Jul 24, 2017

#[doc(hidden)] __Nonexhaustive variants.
@sfackler

This comment has been minimized.

Sign in to view
Copy link
Member

sfackler commented Jul 24, 2017

Also good to talk about when to go with an open enum vs an opaque "normal" type.

@dtolnay dtolnay added the new guideline label Sep 18, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.