about summary refs log tree commit diff
path: root/src
AgeCommit message (Collapse)AuthorLines
2019-02-01Remove unnecessary is_local() checkAaron Hill-2/+1
2019-02-01Test allowing individual struct fieldAaron Hill-0/+6
2019-02-01Replace --extern-public with --extern-privateAaron Hill-36/+36
2019-02-01Remove feature from testAaron Hill-1/+0
2019-02-01Tidy fixesAaron Hill-4/+5
2019-02-01Move --extern-public behind -Z unstable-optionsAaron Hill-24/+29
2019-02-01Remove feature gateAaron Hill-3/+0
2019-02-01Rename external_private_dependency to exported_private_dependenciesAaron Hill-12/+14
2019-02-01Delete dead codeAaron Hill-26/+0
2019-02-01Track extern_public command-line argumentAaron Hill-5/+5
2019-02-01Add test for 'std' crate being publicAaron Hill-0/+13
2019-02-01Clippy fixes, rename stuff to match RFCAaron Hill-13/+32
2019-02-01Improve UI testsAaron Hill-6/+32
2019-02-01Always treat 'std' and 'core' as publicAaron Hill-1/+5
2019-02-01Add UI testAaron Hill-0/+57
2019-02-01Properly register lintAaron Hill-0/+1
2019-02-01Fixup codeAaron Hill-84/+20
2019-02-01Fix emitting lintAaron Hill-18/+31
2019-02-01Initial implementation workAaron Hill-5/+164
2019-02-01Auto merge of #57916 - Zoxc:incr-passes4, r=michaelwoeristerbors-117/+136
Misc performance tweaks r? @michaelwoerister
2019-02-01Fix typoking6cong-1/+1
2019-02-01Stabilize std::error::Error::type_idSimon Sapin-3/+1
This should have been part of https://github.com/rust-lang/rust/pull/57834 FCP: https://github.com/rust-lang/rust/issues/27745#issuecomment-373906749
2019-02-01Fix image link in the settings menuGuillaume Gomez-15/+35
2019-02-01Stabilize split_ascii_whitespaceSimon Sapin-8/+6
Tracking issue FCP to merge: https://github.com/rust-lang/rust/issues/48656#issuecomment-442372750
2019-02-01Don't know why I wasn't using `self` properly thereLokathor-1/+1
2019-02-01Make overflowing and wrapping negation constLokathor-9/+5
Remember that the signed and unsigned versions are slightly different here, so there's four functions made const instead of just two.
2019-02-01Fix `std::os::fortanix_sgx::usercalls::raw::UsercallNrs`Jethro Beekman-20/+10
Fixes https://github.com/fortanix/rust-sgx/issues/88
2019-01-31Fix grammar in E0283 explanationSergei Vorobev-1/+1
2019-02-01Auto merge of #58002 - oli-obk:deprecated_sugg, r=zackmdavisbors-26/+111
Add suggestions to deprecation lints Clippy used to do this suggestion, but the clippy lints happen after the deprecation lints so we ended up never seeing the structured suggestions.
2019-01-31Simplify lambdasLinus Färnstrand-4/+4
2019-01-31Add missing generation for test and proc_macro, remove old macro redirectionGuillaume Gomez-17/+23
2019-01-31Clarify semantics of #[repr(align(x))] on enumsNiklas Fiekas-0/+16
2019-01-31rustdoc: wrap stability tags in colored spansAndy Russell-19/+31
2019-01-31Stabilize the time_checked_add featureLinus Färnstrand-4/+4
2019-01-31Auto merge of #56696 - jonas-schievink:weak-counts, r=alexcrichtonbors-1/+142
Implement Weak::{strong_count, weak_count} The counters are also useful on `Weak`, not just on strong references (`Rc` or `Arc`). In situations where there are still strong references around, you can also get these counts by temporarily upgrading and adjusting the values accordingly. Using the methods introduced here is simpler to do, less error-prone (since you can't forget to adjust the counts), can also be used when no strong references are around anymore, and might be more efficient due to not having to temporarily create an `Rc`. This is mainly useful in assertions or tests of complex data structures. Data structures might have internal invariants that make them the sole owner of a `Weak` pointer, and an assertion on the weak count could be used to ensure that this indeed happens as expected. Due to the presence of `Weak::upgrade`, the `strong_count` becomes less useful, but it still seems worthwhile to mirror the API of `Rc`. TODO: * [X] Tracking issue - https://github.com/rust-lang/rust/issues/57977 Closes https://github.com/rust-lang/rust/issues/50158
2019-01-31Use ensure for mir_borrowckJohn Kåre Alsaker-1/+1
2019-01-31Auto merge of #57914 - jethrogb:jb/sgx-unwind-version, r=alexcrichtonbors-25/+35
SGX target: clean up dist builder, update libunwind This incorporates https://github.com/fortanix/llvm-project/pull/4 Fixes https://github.com/fortanix/rust-sgx/issues/65 r? @alexcrichton
2019-01-31Auto merge of #58003 - nikic:saturating-add, r=nagisabors-3/+101
Use LLVM intrinsics for saturating add/sub Use the `[su](add|sub).sat` LLVM intrinsics, if we're compiling against LLVM 8, as they should optimize and codegen better than IR based on `[su](add|sub).with.overlow`. For the fallback for LLVM < 8 I'm using the same expansion that target lowering in LLVM uses, which is not the same as Rust currently uses (in particular due to the use of selects rather than branches). Fixes #55286. Fixes #52203. Fixes #44500. r? @nagisa
2019-01-31Add more tests for #[repr(align(x))] on enumsNiklas Fiekas-8/+56
2019-01-31Add a forever unstable opt-out of const qualification checksOliver Scherer-2/+155
2019-01-31Updated commit id for building libunwind.Vardhan Thigle-2/+2
2019-01-31Auto merge of #57514 - michaelwoerister:xlto-tests, r=alexcrichtonbors-21/+171
compiletest: Support opt-in Clang-based run-make tests and use them for testing xLTO. Some cross-language run-make tests need a Clang compiler that matches the LLVM version of `rustc`. Since such a compiler usually isn't available these tests (marked with the `needs-matching-clang` directive) are ignored by default. For some CI jobs we do need these tests to run unconditionally though. In order to support this a `--force-clang-based-tests` flag is added to compiletest. If this flag is specified, `compiletest` will fail if it can't detect an appropriate version of Clang. @rust-lang/infra The PR doesn't yet enable the tests yet. Do you have any recommendation for which jobs to enable them? cc #57438 r? @alexcrichton
2019-01-31Add suggestion for duplicated import.David Wood-111/+570
This commit adds a suggestion when a import is duplicated (ie. the same name is used twice trying to import the same thing) to remove the second import.
2019-01-31Rollup merge of #58008 - matthewjasper:places-conflict-args, r=oli-obkMazdak Farrokhzad-1/+37
Pass correct arguments to places_conflict The borrow place *must* be a place that we track borrows for, otherwise we will likely ICE. Closes #57989
2019-01-31Rollup merge of #58007 - estebank:issue-58006, r=petrochenkovMazdak Farrokhzad-1/+26
Don't panic when accessing enum variant ctor using `Self` in match Fix #58006. r? @petrochenkov
2019-01-31Rollup merge of #58005 - vitiral:docs_trim_start_matches, r=ManishearthMazdak Farrokhzad-8/+8
update docs for fix_start/end_matches fixes #57686:
2019-01-31Rollup merge of #58000 - oli-obk:fixes_and_cleanups, r=RalfJungMazdak Farrokhzad-45/+77
Fixes and cleanups Address the points raised in https://github.com/rust-lang/rust/pull/57677/files by @eddyb and @RalfJung
2019-01-31Rollup merge of #57999 - jethrogb:jb/movbe-feature, r=alexcrichtonMazdak Farrokhzad-1/+5
Add MOVBE x86 CPU feature I have no idea if this is correct. I basically copied the ADX feature. I verified the feature is also called `movbe` in LLVM. I marked this to become stable immediately, as part of the RFC 2045. r? @alexcrichton
2019-01-31Rollup merge of #57984 - phansch:improve_check_ty_error, r=zackmdavisMazdak Farrokhzad-2/+2
Improve bug message in check_ty This branch was hit in Clippy and I think it would be nice to show the thing that was unexpected in the bug message. It's also in line with the other `bug!` messages in `check_ty`.
2019-01-31Rollup merge of #57980 - siddharthasahu:patch-1, r=QuietMisdreavusMazdak Farrokhzad-0/+4
Add the edition guide to the bookshelf
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-02-28 22:31:55 +0000