Inconsistent usage of `bool` as success indicator corrupting documentation. about flaxengine HOT 4 OPEN

(though couldn't those just be an int?)

I think this is a good solution.. but an enum might still work if you can implicitly cast it to a bool like you normally can in C++, and in C#. I'm not sure how much benefit there is to using a enum, though.

from flaxengine.

Most of the engine APIs return true on error - design decision based other common programming APIs that return 0/false on success. For stdlib we could improve some return codes such as Dictionary removal to return true when item was properly removed. Also, INetworkDriver APIs need refactor to match results.

Feel free to indicate other APIs that could benefit from this change. Ofc, we won't introduce breaking changes now - that's not critical issue thus I would move such refactor once we start working on Flax 2.

from flaxengine.

+1 for true on success. No preference for status code returns (though couldn't those just be an int?)

from flaxengine.

@envision3d I didn't want int because of idiotic implicit casts to bool (in C++). I would want a compiler to scream at me, if I tried to assign status code value to a bool.

from flaxengine.