bindings: Have NullValue() declarations in either NativeValueTraits or IDLBase (and children), not both |
||||
Issue descriptionThis came up in https://chromium-review.googlesource.com/c/chromium/src/+/831497. Right now we have NativeValueTraits<T>::NullValue() only when T is IDLByteString, IDLString or IDLUSVString. Meanwhile, IDLNullable<T> also implements NullValue(), which is quite confusing. At the moment one of the reasons why we have NVT<T>::NullValue() in the first place is that interface types do not inherit from IDLBase but do use NVT, so it is easier to add methods, variables and typedefs there. It would be good to unify all this in a single place to reduce confusion. (see also: issue 798470)
,
Jan 10 2018
,
Jan 10
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
,
Jan 10
|
||||
►
Sign in to add a comment |
||||
Comment 1 by jbroman@chromium.org
, Jan 2 2018