On 18/06/2020 14:09, Qu Wenruo wrote: >> I find that try_ naming uneasy. If you take the example from locking >> for instance, after a successful mutex_trylock() you still need to call >> mutex_unlock(). > > Yep, I have the same concern, although no good alternative naming. Yeah, there's only two hard things in computer science, cache coherency, naming things and off-by-one errors.
