- User Since
- Nov 3 2018, 6:10 AM (64 w, 2 d)
Sat, Jan 25
It looks like recent change did add a line-break after " (in-process)", so I guess this should be reverted, and instead a patch more or less like this should make it work again:
Aug 19 2019
The only group I know which uses -fsemantic-interposition is the company I work for: Amadeus. Since for now the flag doesn't exist on clang, no we don't know that the future clang implementation doesn't match the gcc one ;) But then we have to wonder if clang wants to reuse the same name if that doesn't do the same thing if really the differences are big. What are the differences between the gcc and the LLVM implementation (when -fsemantic-interposition will be wired up in clang) ?
Aug 3 2019
Thanks Serge. Given that I am only a very occasional contributor, I don't have any right to push this commit myself. Would you please commit it for me ?
Aug 1 2019
Jan 11 2019
Thank you !
Jan 10 2019
Rebased to master
Jan 9 2019
I saw you recently merged some Python 3 related stuff. Here is an older review from November still never reviewed. You fixed already the fix around the lambda, yet I still need to add "universal_newlines" on current trunk otherwise I have some bytes vs str objects error. Do you think you can land this small change too ?
Nov 14 2018
Is there any news on this code review ? Is it ready to land ?