diff options
| author | Tomasz Różański <rosto@tlen.pl> | 2019-07-27 17:55:28 +0200 |
|---|---|---|
| committer | Tomasz Różański <rosto@tlen.pl> | 2019-07-27 22:15:09 +0200 |
| commit | 98c50ebfa124f311f3c889f3cc885df21aaeb31f (patch) | |
| tree | 0a8e6b72bee730496839056790a484cdc35c44b1 /src/libstd/sys | |
| parent | c43753f910aae000f8bcb0a502407ea332afc74b (diff) | |
| download | rust-98c50ebfa124f311f3c889f3cc885df21aaeb31f.tar.gz rust-98c50ebfa124f311f3c889f3cc885df21aaeb31f.zip | |
Change the placement of two functions.
Right now, the order is as follows: `pop_front()` `push_front()` `push_back()` `pop_back()` `swap_remove_back()` `swap_remove_front()` I believe it would be more natural, and easier to follow, if we place `pop_back()` right after the `pop_front()`, and `swap_remove_back()` after the `swap_remove_front()` like this: `pop_front()` `pop_back()` `push_front()` `push_back()` `swap_remove_front()` `swap_remove_back()` The rest of the documentation (at least in this module) adheres to the same logic, where the 'front' function always precedes its 'back' equivalent.
Diffstat (limited to 'src/libstd/sys')
0 files changed, 0 insertions, 0 deletions