You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 17, 2023. It is now read-only.
It is a confusing variable name, but it is not a bug.
The meanings of decay_alloc_ and decay_alloc are different.
The former decay_alloc_ is an argument to decide whether the chunk need to decay-allocated.
But the later decay_alloc is the state whether the memory has not been allocated.
For the two cases decay_alloc_ is true or false,
When the argument decay_alloc_ is true,
decay_alloc = true;
the condition if (!delay_alloc_) does not be satisfied.
When the argument decay_alloc_ is false, the following steps will be executed:
decay_alloc = true;
The condition if (!decay_alloc_) is satisfied, then the function CheckAndAlloc() be called.
Description
I'm confuse about the coding here:
here is source code
question
why not assign
delay_alloc_
todelay_alloc
?The text was updated successfully, but these errors were encountered: