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.

Sign up for GitHub

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

Jump to bottom

Tracking Issue for RFC 36 - ternary #80

Closed
Alex6323 opened this issue Jun 2, 2020 · 0 comments
Closed

Tracking Issue for RFC 36 - ternary #80

Alex6323 opened this issue Jun 2, 2020 · 0 comments
Assignees
@zesterer
Labels
c-tracking-issue Category - Tracking issue e-high Experience - High p-critical Priority - Critical wg-ternary Working Group - Ternary

Comments

@Alex6323
Copy link
Contributor

Alex6323 commented Jun 2, 2020 •
edited by thibault-martinez

This is a tracking issue for RFC 36 - ternary.

About tracking issues

Tracking issues are used to record the overall progress of implementation.
They are also uses as hubs connecting to other relevant issues, e.g., bugs or open design questions.
A tracking issue is however not meant for large scale discussion, questions, or bug reports about a feature.
Instead, open a dedicated issue for the specific matter.

Steps

Unresolved Questions

Implementation history
@Alex6323 Alex6323 added the c-tracking-issue Category - Tracking issue label Jun 2, 2020
@Alex6323 Alex6323 mentioned this issue Jun 2, 2020
Merged
@thibault-martinez thibault-martinez changed the title Tracking Issue for RFC 36 - bee-ternary Tracking Issue for RFC 36 - ternary Jun 2, 2020
@thibault-martinez thibault-martinez added e-high Experience - High p-critical Priority - Critical wg-ternary Working Group - Ternary labels Jun 3, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@zesterer zesterer

Labels
c-tracking-issue Category - Tracking issue e-high Experience - High p-critical Priority - Critical wg-ternary Working Group - Ternary
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@zesterer @thibault-martinez @Alex6323