0e8d571298
Summary: Duplicate category method implementations cause undefined behavior in Objective-C; one is chosen essentially at random. The linker also issues a noisy warning about this (which is how I noticed this case). It didn't matter in this particular case since both implementations do the same thing, but we should clean this up so people don't get desensitized to these linker warnings. There is no need to have two implementations. Reviewed By: fkgozali Differential Revision: D16587219 fbshipit-source-id: 56dc3493735443c476484092f4a7eacfcddee8cb |
||
|---|---|---|
| .. | ||
| Mounting | ||
| Surface | ||
| Utils | ||
| RCTConversions.h | ||
| RCTImageResponseDelegate.h | ||
| RCTImageResponseObserverProxy.h | ||
| RCTImageResponseObserverProxy.mm | ||
| RCTPrimitives.h | ||
| RCTScheduler.h | ||
| RCTScheduler.mm | ||
| RCTSurfacePresenter.h | ||
| RCTSurfacePresenter.mm | ||
| RCTSurfaceRegistry.h | ||
| RCTSurfaceRegistry.mm | ||
| RCTSurfaceTouchHandler.h | ||
| RCTSurfaceTouchHandler.mm | ||
| RCTTouchableComponentViewProtocol.h | ||