diff options
| author | bors <bors@rust-lang.org> | 2019-08-18 22:01:21 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2019-08-18 22:01:21 +0000 |
| commit | 0ccbae2f1878380e6c3777b8b172dfef61c3842b (patch) | |
| tree | d080b72b02e3ca6e2590310054f5436974759a72 /src/libstd/sys/unix/stack_overflow.rs | |
| parent | 4cf7673076e6975532213e494dd3f7f9d8c2328e (diff) | |
| parent | 98c50ebfa124f311f3c889f3cc885df21aaeb31f (diff) | |
| download | rust-0ccbae2f1878380e6c3777b8b172dfef61c3842b.tar.gz rust-0ccbae2f1878380e6c3777b8b172dfef61c3842b.zip | |
Auto merge of #63045 - Rosto75:master, r=jonas-schievink
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/unix/stack_overflow.rs')
0 files changed, 0 insertions, 0 deletions