New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 731893 link

Starred by 1 user
Status: Assigned
Owner:
dcheng@chromium.org
Cc:
█ yzshen@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

Change [Extensible] to require specifying a default enumerator value when deserializing an unknown value

Project Member Reported by dcheng@chromium.org, Jun 9 2017 
This way, the mojom can explicitly define an enum value to treat as the unknown value, and it's easier to verify that handling of unknown enumerator values is correct.

(There was brief discussion about doing this, but I don't think I filed a bug)
Project Member

Comment 1 by sheriffbot@chromium.org, Jun 11 2018

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 2 by oksamyt@chromium.org, Dec 4

Components: -Internals>Mojo Internals>Mojo>Bindings
Labels: -Hotlist-Recharge-Cold
Status: Available (was: Untriaged)

Comment 3 by dcheng@chromium.org, Dec 4

Labels: -Pri-3 Pri-2
Owner: dcheng@chromium.org
Status: Assigned (was: Available)
We should try to do this sooner rather than later, since ARC++ is importing more mojo files from around Chromium and requiring things to be extensible as a result. I'll throw together a draft proposal.

Comment 4 by lhchavez@chromium.org, Jan 7

Cc: -lhchavez@chromium.org
►

Sign in to add a comment