Welcome to the Lounge

struct BLEData {
    let x: Int16   
}

let mpuData = data.withUnsafeBytes {
   (int16Ptr: UnsafePointer<Int16>)->BLEData in
           BLEData(x: Int16(littleEndian: int16Ptr[0]))
}

let mpuData = data.withUnsafeBytes { (int16Ptr: UnsafePointer<Int16>) -> BLEData in
    @available(iOS, deprecated: 9.0)
    func getLatestImage() -> UIImage? {
        return BLEData(x: Int16(littleEndian: int16Ptr[0]))
    }
    return getLatestImage()
}

Copilot's Explanation:

To avoid warnings, you can use the @available attribute to suppress deprecation warnings.

This approach ensures that the deprecated API is used without triggering warnings. Keep in mind that this workaround applies to specific cases where you encounter deprecation warnings

let mpuData: BLEData = data.withUnsafeBytes { rawBufferPointer in
    let int16Ptr = rawBufferPointer.bindMemory(to: Int16.self)
    return BLEData(x: Int16(littleEndian: int16Ptr[0]))
}

chatGPT explained:

Explanation
withUnsafeBytes Closure Type: The closure parameter is specified as rawBufferPointer, which is of type UnsafeRawBufferPointer. This is more general and avoids type inference issues.
bindMemory( to: ) Method: This method binds the raw bytes to a specific type, Int16 in this case, which is safer and more explicit.
Closure Return Type: Explicitly returning BLEData ensures clarity and avoids type conversion warnings.