sys/luid: Added postcondition to luid_get()#12604
Conversation
Stated the obvious in the doc: Altering the LUID returned by luid_get() breaks the guarantee that it is locally unique, as it than could collide with other LUIDs returned by luid_get().
|
If you |
|
I truly believe that the added doc only clarifies what is already the case. So from my point of view this only makes it easier to notice that they all are violating the API. But I assume this could be controversial in the context it now explicitly says all users but one of the API violate the API; so maybe ACK > 1 is needed. |
|
This precondition makes it basically unusable for the originally intended use-case. ^^ |
|
Adding Then this change should be uncontroversial. |
|
I think it is useless for the apprently most common use case. The new doc will only point that clearly out. |
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you want me to ignore this issue, please mark it with the "State: don't stale" label. Thank you for your contributions. |
|
The description is still true though - and we have |
|
Nope, just fine IMHO. Let's just rerun Travis, to be safe. |
|
Thanks for the reviews! |
Contribution description
Stated the obvious in the doc: Altering the LUID returned by
luid_get()breaks the guarantee that it is locally unique, as it than could collide with other LUIDs returned byluid_get().Testing procedure
Read the new documentation and verify its correctness.
Issues/PRs references
Related to #12600, #12592. Incorrect users of this API have been identified by @benpicco in #12592