- 04 12月, 2017 1 次提交
-
-
由 Niko Matsakis 提交于
Rather than declaring some region variables to be constant, and reporting errors when they would have to change, we instead populate each free region X with a minimal set of points (the CFG plus end(X)), and then we let inference do its thing. This may add other `end(Y)` points into X; we can then check after the fact that indeed `X: Y` holds. This requires a bit of "blame" detection to find where the bad constraint came from: we are currently using a pretty dumb algorithm. Good place for later expansion.
-
- 18 11月, 2017 1 次提交
-
-
由 Taylor Cramer 提交于
After this change, impl Trait existentials are desugared to a new `abstract type` definition paired with a set of lifetimes to apply. In-scope generics are included as parents of the `abstract type` generics. Parent regions are replaced with static, and parent regions referenced in the `impl Trait` type are duplicated at the end of the `abstract type`'s generics.
-
- 16 11月, 2017 1 次提交
-
-
由 Niko Matsakis 提交于
-
- 02 11月, 2017 1 次提交
-
-
由 Niko Matsakis 提交于
-
- 25 9月, 2017 1 次提交
-
-
由 Esteban Küber 提交于
On "the parameter type `T` may not live long enough" error, point to the parameter type suggesting lifetime bindings: ``` error[E0310]: the parameter type `T` may not live long enough --> $DIR/lifetime-doesnt-live-long-enough.rs:28:5 | 27 | struct Foo<T> { | - help: consider adding an explicit lifetime bound `T: 'static`... 28 | foo: &'static T | ^^^^^^^^^^^^^^^ | note: ...so that the reference type `&'static T` does not outlive the data it points at --> $DIR/lifetime-doesnt-live-long-enough.rs:28:5 | 28 | foo: &'static T | ^^^^^^^^^^^^^^^ ```
-
- 11 9月, 2017 1 次提交
-
-
由 Eduard-Mihai Burtescu 提交于
-
- 02 9月, 2017 1 次提交
-
-
由 Eduard-Mihai Burtescu 提交于
-
- 17 6月, 2017 1 次提交
-
-
由 Niko Matsakis 提交于
-
- 13 5月, 2017 3 次提交
-
-
由 Eduard-Mihai Burtescu 提交于
-
由 Eduard-Mihai Burtescu 提交于
-
由 Eduard-Mihai Burtescu 提交于
-
- 01 5月, 2017 4 次提交
-
-
由 Taylor Cramer 提交于
Instead of requesting the region maps for the entire crate, request for a given item etc. Several bits of code were modified to take `&RegionMaps` as input (e.g., the `resolve_regions_and_report_errors()` function). I am not totally happy with this setup -- I *think* I'd rather have the region maps be part of typeck tables -- but at least the `RegionMaps` works in a "parallel" way to `FreeRegionMap`, so it's not too bad. Given that I expect a lot of this code to go away with NLL, I didn't want to invest *too* much energy tweaking it.
-
由 Niko Matsakis 提交于
Make a `CodeExtent<'tcx>` be something allocated in an arena instead of an index into the `RegionMaps`.
-
由 Niko Matsakis 提交于
Instead, thread around `Option<CodeExtent>` where applicable.
-
由 Taylor Cramer 提交于
-
- 12 4月, 2017 2 次提交
-
-
由 Michael Woerister 提交于
-
由 Niko Matsakis 提交于
-
- 28 2月, 2017 1 次提交
-
-
由 Niko Matsakis 提交于
-
- 01 9月, 2016 1 次提交
-
-
由 Ariel Ben-Yehuda 提交于
The warnings have already reached stable The test rfc1592_deprecated is covered by `bad_sized` and `unsized6`. Fixes #33242 Fixes #33243
-
- 27 8月, 2016 1 次提交
-
-
由 Eduard Burtescu 提交于
-
- 11 5月, 2016 4 次提交
-
-
由 Eduard Burtescu 提交于
-
由 Eduard Burtescu 提交于
-
由 Eduard Burtescu 提交于
-
由 Eduard Burtescu 提交于
-
- 03 5月, 2016 1 次提交
-
-
由 Ariel Ben-Yehuda 提交于
this commit should be reverted after a release cycle
-
- 07 4月, 2016 1 次提交
-
-
由 Masood Malekghassemi 提交于
-
- 01 4月, 2016 1 次提交
-
-
由 Benjamin Herr 提交于
-
- 27 3月, 2016 1 次提交
-
-
由 Eduard Burtescu 提交于
-
- 03 3月, 2016 1 次提交
-
-
由 Jeffrey Seyfried 提交于
-
- 05 10月, 2015 1 次提交
-
-
由 Ms2ger 提交于
-
- 14 9月, 2015 1 次提交
-
-
由 Ariel Ben-Yehuda 提交于
-
- 25 8月, 2015 3 次提交
-
-
由 Ariel Ben-Yehuda 提交于
-
由 Ariel Ben-Yehuda 提交于
this makes the code cleaner
-
由 Ariel Ben-Yehuda 提交于
This increases regionck performance greatly - type-checking on librustc decreased from 9.1s to 8.1s. Because of Amdahl's law, total performance is improved only by about 1.5% (LLVM wizards, this is your opportunity to shine!). before: 576.91user 4.26system 7:42.36elapsed 125%CPU (0avgtext+0avgdata 1142192maxresident)k after: 566.50user 4.84system 7:36.84elapsed 125%CPU (0avgtext+0avgdata 1124304maxresident)k I am somewhat worried really need to find out why we have this Red Queen's Race going on here. Originally I suspected it may be a problem from RFC1214's warnings, but it seems to be an effect from other changes. However, the increase seems to be mostly in LLVM's time, so I guess it's the LLVM wizards' problem.
-
- 22 8月, 2015 3 次提交
-
-
由 Niko Matsakis 提交于
-
由 Niko Matsakis 提交于
-
由 Niko Matsakis 提交于
-
- 21 8月, 2015 1 次提交
-
-
由 Niko Matsakis 提交于
-
- 19 8月, 2015 1 次提交
-
-
由 Niko Matsakis 提交于
`TransitiveRelation`
-
- 13 8月, 2015 1 次提交
-
-
由 Niko Matsakis 提交于
-