alphabetize

[ddudt]

No code is changed, only sorting the files in alphabetical order. The following rules are applied:

1. Classes first, then functions
2. Underscores come before numbers
3. Numbers come before letters

The only exception is that getter & setter methods are at the end of a class, instead of being mixed in with the other methods.

To-do:

• compute
• equilibrium
• geometry
• io
• objectives
• optimize
• other desc/
• tests

[codecov]

Codecov Report

Merging #630 (47ba479) into master (74e8faa) will increase coverage by 5.69%.
The diff coverage is 95.38%.

❗ Current head 47ba479 differs from pull request most recent head 817a243. Consider uploading reports for the commit 817a243 to get more accurate results

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #630      +/-   ##
==========================================
+ Coverage   88.68%   94.37%   +5.69%     
==========================================
  Files          78       77       -1     
  Lines       18520    17896     -624     
==========================================
+ Hits        16424    16889     +465     
+ Misses       2096     1007    -1089     

Files Changed	Coverage Δ
desc/equilibrium/equilibrium.py	96.34% <ø> (+9.99%)	⬆️
desc/objectives/linear_objectives.py	97.41% <ø> (+1.61%)	⬆️
desc/plotting.py	88.38% <ø> (+13.79%)	⬆️
desc/io/pickle_io.py	67.56% <66.66%> (+29.72%)	⬆️
desc/io/hdf5_io.py	80.89% <85.45%> (+16.29%)	⬆️
desc/io/equilibrium_io.py	85.89% <87.17%> (+6.41%)	⬆️
desc/utils.py	90.40% <88.42%> (+1.84%)	⬆️
desc/interpolate.py	86.46% <89.34%> (+28.82%)	⬆️
desc/equilibrium/initial_guess.py	95.00% <89.47%> (+1.76%)	⬆️
desc/derivatives.py	94.07% <90.72%> (+6.82%)	⬆️
... and 20 more

... and 32 files with indirect coverage changes

[f0uriest]

OK, spent the past few days playing with this and the script to alphabetize things works fine, but we still get tons of merge conflicts, even if we sort both branches first. Git sees that both branches modified the same lines, even if they're modified to be the same. Resolving all the merge conflicts is a huge pain, and even when I was super careful I still missed stuff and either lost changes or included changes that shouldn't have been.

I'm going to vote that we shelve this, as I don't think the benefit is worth all the aggravation, especially when we can just Ctrl-F to find whatever function/method etc we want in a given file. For now I'm going to unsort #484 so we can get that in cleanly.