You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The number is there because there is such a test for each T that is used as nsTArray<T>. Furthermore, the counting is global -- adding another instantiation will renumber all such tests, not just the array ones. This means that nontrivial binding updates are very prone to bitrot.
Instead of numbering this we should do something like fn __bindgen_test_layout_nsTArray_lt_nsCString_gt_instantiation. Basically, some mangling scheme that can reliably produce unique names.
Currently bindgen generates a lot of tests like so:
The number is there because there is such a test for each
T
that is used asnsTArray<T>
. Furthermore, the counting is global -- adding another instantiation will renumber all such tests, not just the array ones. This means that nontrivial binding updates are very prone to bitrot.Instead of numbering this we should do something like
fn __bindgen_test_layout_nsTArray_lt_nsCString_gt_instantiation
. Basically, some mangling scheme that can reliably produce unique names.cc @emilio
The text was updated successfully, but these errors were encountered: