Documented Behaviour != Implemented Behaviour
Posted Feb 2, 2020, 3:07 PM UTC
8210
That assignment can never fail, so there's nothing wrong here.
7
Cold have been left over from manual memory allocation or prepared for introduction of manual memory management.
3
interface != implementation
or, "I'll write it later..."
2
To send the value to the remote device, call writeCharacteristic to send the value to the remote device.
Yes, and longcat is long.
1
int getRandomNumber() {
return 4; // chosen by fair dice roll, garunteed to be random
}
1
Runs multiple times and keeps getting 4. Huh I’m really lucky I guess
1
Lemme guess... Implementing autogenerated stub provided by some "architect"? (-:
0
It just never fails!! :) :) :)
Not enough information to tell- it could be overridden in a subclass or something.
Technically the implementation matches the documentation, since if there is some reason that it failed, it would result in an exception before it returns true.