Eric O'Connell09/29/2023, 9:47 PM
, etc. However, in doing so I am taking kotlin values that are natively representable in JSON (e.g.,
) and then converting them to strings (in construction of
), and then transforming them back to strings, which ends up calling
… given that this data represents large lists of 2d coordinates, I am seeing times in excess of 185ms for relatively small documents on Android devices. My main question: is there a way to avoid this double-conversion penalty so I can go directly from kotlin -> json string?