Re: [accelerometer] Why unrestricted double for acceleration readings?

Think it was supposed to mean "unset value" but now the reading properties are nullable so no need to keep them `unrestricted`.

GitHub Notification of comment by pozdnyakov
Please view or discuss this issue at using your GitHub account

Received on Wednesday, 20 September 2017 08:54:09 UTC