Remove comments

Author: m-bert

packages/react-native-gesture-handler/android/src/main/java/com/swmansion/gesturehandler/react/events/RNGestureHandlerTouchEvent.kt

@@ -69,13 +69,7 @@ class RNGestureHandlerTouchEvent private constructor() : Event<RNGestureHandlerT
       putInt("eventType", handler.touchEventType)
       putInt("pointerType", handler.pointerType)
 
-      // Both keys have to be present in every touch event, otherwise the JS side may
-      // misclassify it as an update event and crash trying to read gesture-specific data.
-      // The payloads may be null when the tracked pointers were cleared before the event
-      // was serialized (e.g. the gesture was cancelled by a rapid succession of taps) or
-      // when the payload was already consumed - fall back to empty arrays, matching iOS.
       putArray("changedTouches", handler.consumeChangedTouchesPayload() ?: Arguments.createArray())
-
       putArray("allTouches", handler.consumeAllTouchesPayload() ?: Arguments.createArray())
 
       if (handler.isAwaiting && handler.state == GestureHandler.STATE_ACTIVE) {

packages/react-native-gesture-handler/src/v3/hooks/callbacks/eventHandler.ts

@@ -150,11 +150,7 @@ export function eventHandler<
     return;
   }
 
-  // At this point the event should be an update event carrying `handlerData`.
-  // If it isn't, it's a malformed event (e.g. a touch event that lost its
-  // `allTouches` payload in a race on the native side) - drop it instead of
-  // running the change calculator on undefined data, which would crash the UI
-  // thread.
+  // Guard against malformed events
   if (eventWithData.handlerData === undefined) {
     return;
   }

packages/react-native-gesture-handler/src/v3/hooks/utils/eventUtils.ts

@@ -119,10 +119,7 @@ export function getChangeEventCalculator<TExtendedHandlerData>(
     'worklet';
     const currentEventData = current.handlerData;
 
-    // Events missing `handlerData` cannot have their change payload computed.
-    // This shouldn't happen for well-formed update events, but a malformed
-    // event (e.g. a touch event that lost its payloads in a race on the native
-    // side) must not crash the diff calculator on the UI thread.
+    // Guard against malformed events
     if (currentEventData === undefined) {
       return current;
     }