File tree Expand file tree Collapse file tree 2 files changed +3
-3
lines changed
branches/beta/src/librustc_data_structures Expand file tree Collapse file tree 2 files changed +3
-3
lines changed Original file line number Diff line number Diff line change @@ -23,7 +23,7 @@ refs/tags/0.9: 36870b185fc5f5486636d4515f0e22677493f225
23
23
refs/tags/0.10: ac33f2b15782272ae348dbd7b14b8257b2148b5a
24
24
refs/tags/0.11.0: e1247cb1d0d681be034adb4b558b5a0c0d5720f9
25
25
refs/tags/0.12.0: f0c419429ef30723ceaf6b42f9b5a2aeb5d2e2d1
26
- refs/heads/beta: 63eedfcf536f02e09e7dca7290b803ad8aa243f9
26
+ refs/heads/beta: 57909f7068c5a2fb63f15bc43a7d3e823205608a
27
27
refs/tags/1.0.0-alpha: e42bd6d93a1d3433c486200587f8f9e12590a4d7
28
28
refs/heads/tmp: 370fe2786109360f7c35b8ba552b83b773dd71d6
29
29
refs/tags/1.0.0-alpha.2: 4c705f6bc559886632d3871b04f58aab093bfa2f
Original file line number Diff line number Diff line change @@ -211,7 +211,7 @@ impl<T:Debug+PartialEq> TransitiveRelation<T> {
211
211
// - In the example above, we would reverse to
212
212
// `[z, y, x]` and then pare down to `[z]`.
213
213
// 4. Reverse once more just so that we yield a vector in
214
- // increasing order of index. Maybe this is silly .
214
+ // increasing order of index. Not necessary, but why not .
215
215
//
216
216
// I believe this algorithm yields a minimal set. The
217
217
// argument is that, after step 2, we know that no element
@@ -224,11 +224,11 @@ impl<T:Debug+PartialEq> TransitiveRelation<T> {
224
224
pare_down ( & mut candidates, closure) ; // (2)
225
225
candidates. reverse ( ) ; // (3a)
226
226
pare_down ( & mut candidates, closure) ; // (3b)
227
- candidates. reverse ( ) ; // (4)
228
227
candidates
229
228
} ) ;
230
229
231
230
lub_indices. into_iter ( )
231
+ . rev ( ) // (4)
232
232
. map ( |i| & self . elements [ i] )
233
233
. collect ( )
234
234
}
You can’t perform that action at this time.
0 commit comments