Message288471
> I'm not sure using this flag impacts on consistency with CFFI
I meant consistency with respect to supported argument types. If someone contributed a workaround to CFFI, then I would rather port it, but it looks like they're also waiting for this to be addressed upstream.
It occurs to me that in the 1st pass, it also needs to propagate the non-argument flag from any field that has it set. This should be done for all platforms, not just X86_64. |
|
Date |
User |
Action |
Args |
2017-02-23 19:26:24 | eryksun | set | recipients:
+ eryksun, vinay.sajip, amaury.forgeotdarc, belopolsky, weeble, meador.inge, Ilya.Kulakov, alexei.romanov |
2017-02-23 19:26:24 | eryksun | set | messageid: <1487877984.15.0.0938984303775.issue22273@psf.upfronthosting.co.za> |
2017-02-23 19:26:24 | eryksun | link | issue22273 messages |
2017-02-23 19:26:24 | eryksun | create | |
|