Ergonomics of UUID::B128(u8vec)

[osynge]

As I understand it UUID::B128(u8vec) takes a vector of u8 in the reverse order to that displayed. This is confusing an not ergonomic.

for example the code:

let authcharuuid : [u8; 16] = [ 0x67, 0xDF , 0xD1, 0x30, 0x42, 0x16, 0x39, 0x89, 0xE4, 0x11, 0xE9, 0x47, 0x30, 0xEE , 0xE9, 0x47];
println!("UUID:{}",  UUID::B128(authcharuuid)); 

produces the output:

UUID:47:E9:EE:30:47:E9:11:E4:89:39:16:42:30:D1:DF:67

[JJJollyjim]

FWIW, this behavior matches the other BLE API I have used, for the ESP32:

https://github.com/espressif/esp-idf/blob/master/examples/bluetooth/gatt_server_service_table/main/gatts_table_creat_demo.c#L88

I definitely found it confusing when using that library

[visceralfield]

This behaviour is also found in Nordic Semiconductor's BLE libraries - it's about host vs. network byte order.