about summary refs log tree commit diff
path: root/src
AgeCommit message (Collapse)AuthorLines
2017-12-31Use memchr for [i8]::contains as wellManish Goregaokar-0/+8
2017-12-13Support 16 bit platformsManish Goregaokar-0/+6
2017-12-13Use memchr in [u8]::containsManish Goregaokar-1/+17
2017-12-13Move rust memchr impl to libcoreManish Goregaokar-232/+234
2017-12-12Auto merge of #46647 - varkor:contrib-1, r=sfacklerbors-0/+8
Add `std::fmt::Pointer` implementation for `AtomicPtr` Resolves #29212.
2017-12-12Auto merge of #46250 - canndrew:rename-never-type-impl-gate, r=petrochenkovbors-8/+8
Rename never_type_impls gate We no longer need a separately-named `never_type_impls` gate thanks to https://github.com/rust-lang/rust/issues/43089.
2017-12-12Auto merge of #46674 - malbarbo:undist-armv5te, r=alexcrichtonbors-6/+1
Remove armv5te target from dist-various-1 Reverts https://github.com/rust-lang/rust/pull/46498 I must have made some mistake when I tested that commit and thought armv5te target worked. but testing it now the produced binaries segfaults (https://github.com/rust-lang/rust/pull/46498#issuecomment-350599233). I tried using crosstool-ng and buildroot toolchain (for armv5te) but the produced binaries also segfaults. Maybe there is a issue with the target, but I cannot investigate it any further. I think the best for now is not to distribute the armv5te target. I'm sorry for what happened.
2017-12-12Auto merge of #46598 - davidtwco:issue-46471, r=arielb1bors-51/+297
MIR borrowck: error message confuses locals and temporaries Fixes #46471 and fixes #46472 (see [this Gitter comment](https://gitter.im/rust-impl-period/WG-compiler-nll?at=5a2d5cb53ae2aa6b3facf0c2)). r? @arielb1
2017-12-12Rename never_type_impls gate to never_typeAndrew Cann-8/+8
2017-12-12Auto merge of #46411 - rillian:str_ascii, r=kennytmbors-24/+24
Mark ascii methods on primitive types stable in 1.23.0 not 1.21.0. The ascii_methods_on_intrinsics feature stabilization didn't land in time for 1.21.0. Update the annotation so the documentation is correct about when these methods became available.
2017-12-12Auto merge of #46657 - nikomatsakis:resolve-lifetimes-query, r=arielb1bors-647/+937
move `resolve_lifetimes` into a proper query Now that we made `resolve_lifetimes` into a query, elision errors no longer abort compilation, which affects some tests. Also, remove `dep_graph_crosscontaminate_tables` -- there is no a path in the dep-graph, though red-green handles it. The same scenario is (correctly) tested by issue-42602.rs in any case. r? @michaelwoerister
2017-12-11Remove armv5te target from dist-various-1Marco A L Barbosa-6/+1
Reverts https://github.com/rust-lang/rust/pull/46498 I must have made some mistake when I tested that commit and thought armv5te target worked. but testing it now the produced binaries segfaults (https://github.com/rust-lang/rust/pull/46498#issuecomment-350599233). I tried using crosstool-ng and buildroot toolchain (for armv5te) but the produced binaries also segfaults. Maybe there is a issue with the target, but I cannot investigate it any further. I think the best for now is not to distribute the armv5te target. I'm sorry for what happened.
2017-12-11Updated existing tests with new error messages.David Wood-46/+57
2017-12-11Refactored and tidied up report functionDavid Wood-53/+92
2017-12-11Auto merge of #46608 - estebank:resolve-return, r=nikomatsakisbors-7/+51
Resolve type on return type suggestion Partially address #45871.
2017-12-11make `krate` infallibleNiko Matsakis-4/+3
2017-12-11Fixed case where borrowed value lives until after scopeDavid Wood-8/+69
2017-12-11Fix error does not know about free/named lifetimesDavid Wood-11/+26
2017-12-11Added test for #46472David Wood-1/+65
2017-12-11Fix error message confuses locals and temporariesDavid Wood-10/+22
2017-12-11Added test for #46471David Wood-0/+44
2017-12-11Auto merge of #46558 - arielb1:union-borrow-refactor, r=nikomatsakisbors-1336/+1358
Clean up the MIR borrowck code I want to avoid the new code to start with so much technical debt. r? @nikomatsakis
2017-12-11move `resolve_lifetimes` into a proper queryNiko Matsakis-237/+283
Now that we made `resolve_lifetimes` into a query, elision errors no longer abort compilation, which affects some tests. Also, remove `dep_graph_crosscontaminate_tables` -- there is no a path in the dep-graph, though red-green handles it. The same scenario is (correctly) tested by issue-42602.rs in any case.
2017-12-11resolve_lifetime: rustfmtNiko Matsakis-476/+721
2017-12-11Auto merge of #46640 - tommyip:ui_tests, r=estebankbors-203/+253
Enforce successful ui tests to have must-compile-successfully flag. r? @nikomatsakis cc @oli-obk Fixes #46587
2017-12-11Auto merge of #46625 - emilio:moar-nits, r=kennytmbors-1/+1
infer: Fix typo in README. Was just reading through it and found this, not a big deal but...
2017-12-11Auto merge of #46624 - emilio:nit, r=kennytmbors-4/+4
rustc_trans: Fix indentation in trans_set_discr. Just noticed this while reading through #46521, which introduced this weird alignment.
2017-12-10Auto merge of #46248 - ↵bors-24/+148
zackmdavis:one_time_private_enum_variant_reexport_error, r=estebank one-time diagnostics for private enum variants glob reëxport ![private_enum_reexport](https://user-images.githubusercontent.com/1076988/33224719-4e5805f0-d121-11e7-8bc0-a708a277a5db.png) r? @estebank
2017-12-10Add `std::fmt::Pointer` implementation for `AtomicPtr`varkor-0/+8
Resolves #29212.
2017-12-10Update ui tests' line numbers.Tommy Ip-192/+192
2017-12-10Add must-compile-successfully comment to appropriate ui tests.Tommy Ip-0/+44
2017-12-10Imply must-compile-successfully in ui-tests when the run-pass flag is present.Tommy Ip-4/+6
2017-12-10Enforce successful ui tests to have must-compile-successfully flag.Tommy Ip-7/+11
2017-12-10Auto merge of #46232 - canndrew:never-docs, r=QuietMisdreavusbors-1/+135
Add docs for never primitive cc @nikomatsakis, @QuietMisdreavus
2017-12-10rustc_trans: Fix indentation in trans_set_discr.Emilio Cobos Álvarez-4/+4
Just noticed this while reading through #46521, which introduced this weird alignment.
2017-12-10infer: Fix typo in README.Emilio Cobos Álvarez-1/+1
Was just reading through it and found this, not a big deal but...
2017-12-10Auto merge of #46620 - bjorn3:remove-test-metric, r=kennytmbors-62/+13
Remove *MetricFn fixes #44808
2017-12-10centralize `does_not_live_long_enough` error reportingAriel Ben-Yehuda-83/+89
2017-12-10remove is_uniqueAriel Ben-Yehuda-74/+15
2017-12-10use `places_conflict` to handle reassignmentAriel Ben-Yehuda-52/+56
This fixes the handling of reassignment of struct fields.
2017-12-10avoid passing the gen/kill bits to `start_block_effects`Ariel Ben-Yehuda-23/+23
If the gen/kill bits are set there, the effects of `start_block_effects` will not be seen when using `FlowAtLocation` etc. to go over the MIR. EverInitializedLvals is the only pass that got this wrong, but this fixes the footgun for everyone.
2017-12-10clean up reassignment duplicate error preventionAriel Ben-Yehuda-16/+40
2017-12-10move FlowAtLocation to be a dataflow abstractionAriel Ben-Yehuda-415/+378
We can now use it in e.g. drop elaboration if we want to.
2017-12-10start extracting things into modulesAriel Ben-Yehuda-1048/+1132
The borrow_check module is too big for its own good
2017-12-10Remove *MetricFnbjorn3-62/+13
2017-12-10Update never_type docs based on feedbackAndrew Cann-1/+2
2017-12-10Auto merge of #46611 - GuillaumeGomez:type-mismatch, r=petrochenkovbors-1/+26
Fix switched types in type mismatch Fixes #46609.
2017-12-10Auto merge of #46602 - mbrubeck:try, r=kennytmbors-230/+92
Replace option_try macros and match with ? operator None
2017-12-09one-time diagnostic and suggestion for reëxporting private variant errorZack M. Davis-10/+109
We issue just one message for an erroneous glob private variant reëxport (using the Session's one-time-diagnostics capability), but individual (non-glob) such erroneous reëxports still get their own messages. The suggestion to make the enum public is also one-time. The enum variant reëxport error didn't have an associated error code (and remedying this here is deemed out of the scope of this commit), so we resort to the expediency of using 0 as the `DiagnosticMessageId` value. Adding Debug to NameResolution was helpful in development. This resolves #46209.
2017-12-09one-time diagnostics: span_suggestion, generalize methods for non-lintsZack M. Davis-14/+39
304c8b1edabcd made the Session's one-time-diagnostics set take a special-purpose `DiagnosticMessageId` enum rather than a LintID so that it could support more than just lints, but the `diag_span_note_once` and `diag_note_once` methods continued to take references to lints: for API consistency, we now make these methods take a `DiagnosticMessageId` while we add support for one-time span-suggestions.
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-04-27 02:41:36 +0000