Nika Layzell e71ae1642c Bug 1535486 - Handle the element type correctly with rust XPCOM types, r=mccr8 ... Before the Array<T> type, the calltype argument could be in, out, or inout, however with Array<T> the element type was added. When I added Array<T>, I changed the checks in files which check calltype != 'in' to instead check 'out' in calltype, such that element would act more like in in most cases (not adding the outparam *). However, I never made that change for rust code, as it didn't support Array<T> at the time. When I turned on Array<T> support for rust code, I forgot to go through and change the conditions, which lead to this bug. Differential Revision: https://phabricator.services.mozilla.com/D24283 --HG-- extra : moz-landing-system : lando		2019-03-22 21:32:59 +00:00
..
xpidl	Bug 1535486 - Handle the element type correctly with rust XPCOM types, r=mccr8	2019-03-22 21:32:59 +00:00
setup.py	…