View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0030637 | Documentation | Manual Content | Public | 2019-03-20 09:50 | 2020-03-23 09:20 |
Reporter | Scott Dunbar | Assigned To | Mark Alexander | ||
Priority | Medium | Severity | C - General | Reproducibility | 100% |
Status | Closed | Resolution | Fixed | ||
Product Version | 2.2.2 | ||||
Target Version | 2.2.3 | Fixed in Version | 2.2.3 | ||
Summary | 0030637: Documentation: ds_priority_find_xxx documentation states that items of equal priority are returned in FIFO order | ||||
Description | Issue: The pages of the documentation for ds_priority_find_min/max and ds_priority_delete_min/max, state that: "If more than one value has the same priority, the one that was added to the priority queue first will be the one to get removed...". This is not the case and as per comments from this issue: https://bugs.yoyogames.com/view.php?id=26111 it is not intended to work this way and entries with the same priority have no guaranteed order. | ||||
Steps To Reproduce | 1. Open help documentation 2. Navigate to pages ds_priority_find_min/max and ds_priority_delete_min/max 3. Observe issues in the description | ||||
Tags | Documentation | ||||
related to | 0031684 | Resolved | Manual Content: ds_priority_delete_...() pages state that items of equal priority are returned in FIFO order |