about summary refs log tree commit diff
path: root/src
AgeCommit message (Collapse)AuthorLines
2019-02-17Add regression test for a specialization-related ICE (#39448)emlai-0/+62
2019-02-17Bump the bootstrap compilerJonas Schievink-1/+1
2019-02-17Changed feature gate for new PathBuf methodsAaron Stillwell-7/+7
Feature gate changed to `path_buf_capacity` as per advice from @Mark-Simulacrum
2019-02-17Fixes for implementation of PathBuf methods (aliases for OsString)Aaron Stillwell-19/+19
- Fixed incorrect `mut` usage - Fixed style in accordance with tidy - Marked all methods as unstable - Changed feature identifier to path_buf_alias_os_string_methods
2019-02-17Modify doctest's auto-`fn main()` to allow `Result`sAndre Bogus-4/+51
This lets the default `fn main()` unwrap any `Result`s, which allows the use of `?` in most tests without adding it manually.
2019-02-17publish_toolstate.py: further fix the runtime errorskennytm-3/+3
The regex was missing a `,`, causing `relevant_pr_match` to become None and set the PR number to -1 and assigned the new issue to `@<unknown user>`. This causes the 422 error when creating the issue due to invalid assignee and unable to leave the tool-is-broken comment since PR -1 does not exist. The default user names are now also changed to @ghost to prevent the 422 error in case anything goes wrong again.
2019-02-17Add alias methods to PathBuf for underlying OsStringAaron Stillwell-1/+81
Implemented the following methods on PathBuf which forward to the underlying OsString. - capacity - with_capacity - clear - reserve - reserve_exact - shrink_to_fit - shrink_to
2019-02-17Auto merge of #58416 - cuviper:dist-linux-gcc, r=alexcrichtonbors-111/+312
[CI] Update GCC in the dist-linux builders Upstream LLVM is planning to raise their minimum toolchain requirements, so they may start using C++14 features. This new policy has already landed in the form of a "soft" error. http://lists.llvm.org/pipermail/llvm-dev/2019-February/130117.html For GCC, they will require at least version 5.1. This PR moves our crosstool-ng builders to their max GCC 5.2, with a few small patches to fix compatibility. The dist-x86_64-linux builder is updated to GCC 5.5 and LLVM/Clang 8.0.0-rc2, which also affects dist-i686-linux sharing the same scripts. r? @alexcrichton
2019-02-17Remove UB in test_ptr_subtraction testKonrad Borowski-2/+4
2019-02-17Remove UB in test_is_null testKonrad Borowski-3/+2
2019-02-17Mention capping forbid lintsDale Wijnand-1/+3
I felt the description of forbid was misleading/incomplete without mentioning how --cap-lints interacts with it.
2019-02-17update stdsimdRalf Jung-0/+0
2019-02-17Auto merge of #58495 - kennytm:rollup, r=kennytmbors-300/+819
Rollup of 19 pull requests Successful merges: - #57929 (Rustdoc remove old style files) - #57981 (Fix #57730) - #58074 (Stabilize slice_sort_by_cached_key) - #58196 (Add specific feature gate error for const-unstable features) - #58293 (Remove code for updating copyright years in generate-deriving-span-tests) - #58306 (Don't default on std crate when manipulating browser history) - #58359 (librustc_mir: use ? in impl_snapshot_for! macro) - #58395 (Instant::checked_duration_since) - #58429 (fix Box::into_unique effecitvely transmuting to a raw ptr) - #58433 (Update which libcore/liballoc tests Miri ignores, and document why) - #58438 (Use posix_spawn_file_actions_addchdir_np when possible) - #58440 (Whitelist the ARM v6 target-feature) - #58448 (rustdoc: mask `compiler_builtins` docs) - #58468 (split MaybeUninit into several features, expand docs a bit) - #58479 (compile-pass test for #53606) - #58489 (Fix runtime error in generate-keyword-tests) - #58496 (Fix documentation for std::path::PathBuf::pop) - #58509 (Notify myself when Clippy toolstate changes) - #58521 (Fix tracking issue for error iterators)
2019-02-16Monomorphize less code in fs::{read|write}Scott McMurray-9/+18
Since the generic-ness is only for the as_refs, might as well have std just compile the important part once instead of on every use.
2019-02-17Rollup merge of #58521 - sfackler:error-iter-issue, r=withoutboatskennytm-4/+4
Fix tracking issue for error iterators
2019-02-17Rollup merge of #58509 - phansch:add_myself_to_clippy_toolstate_maintainers, ↵kennytm-179/+218
r=oli-obk Notify myself when Clippy toolstate changes
2019-02-17Rollup merge of #58496 - nathan:doc-std-path-pathbuf-pop, r=frewsxcvkennytm-2/+1
Fix documentation for std::path::PathBuf::pop Closes #58474.
2019-02-17Rollup merge of #58395 - vi:checked_duration_since, r=dtolnaykennytm-0/+61
Instant::checked_duration_since
2019-02-17Rollup merge of #57929 - GuillaumeGomez:rustodc-remove-old-style-files, ↵kennytm-23/+64
r=ollie27 Rustdoc remove old style files Reopening of #56577 (which I can't seem to reopen...). I made the flag unstable so with this change, what was blocking the PR is now gone I assume.
2019-02-17Rollup merge of #58489 - xfix:fix-keyword-tests-runtime-error, r=alexcrichtonkennytm-2/+2
Fix runtime error in generate-keyword-tests The script was made unusable after removing license headers.
2019-02-17Rollup merge of #58479 - saleemjaffer:test_promote_evaluation_unused_result, ↵kennytm-0/+8
r=oli-obk compile-pass test for #53606 fixes #53606
2019-02-17Don't use an allocation for ItemId in StmtKindJohn Kåre Alsaker-6/+7
2019-02-17Auto merge of #58477 - rust-lang:fix-publish-toolstate-syntax-error, r=oli-obkbors-3/+3
Fix the syntax error in publish_toolstate.py
2019-02-16ui test for directed quote help suggestion #58436Patrick McCarter-0/+19
2019-02-16help suggestion when trying to delimit string literals with directed unicode ↵Patrick McCarter-9/+44
quotes #58436
2019-02-16implement nth_back for BoxAdrian Friedli-0/+4
2019-02-16Fix tracking issue for error iteratorsSteven Fackler-4/+4
2019-02-16Limit the visibility further and expand on a commentOliver Scherer-2/+3
2019-02-16Update docs and visibilities of const to op methodsOliver Scherer-3/+3
2019-02-16Add `eval` prefix to clarify what the function doesOliver Scherer-3/+3
2019-02-16Make `may_normalize` explicit in the type systemOliver Scherer-34/+38
2019-02-16Make validity checking use `MPlaceTy` instead of `OpTy`Oliver Scherer-20/+17
2019-02-16Update src/librustc_mir/interpret/operand.rsRalf Jung-1/+1
Co-Authored-By: oli-obk <github35764891676564198441@oli-obk.de>
2019-02-16Reintroduce the invariant comment for clarityOliver Scherer-0/+1
2019-02-16Reuse the `Pointer` type instead of passing reassembling it at many use sitesOliver Scherer-23/+20
2019-02-16Add a test for const parameter uppercase lintvarkor-0/+27
2019-02-16Don't abort early when collecting const genericsvarkor-4/+19
2019-02-16Check for Const param in collectvarkor-4/+4
2019-02-16Burn some invariants we keep up into codeOliver Scherer-3/+3
2019-02-16Remove an intermediate value from discriminant readingOliver Scherer-3/+3
2019-02-16Expose const -> op functions that don't allow violiting const eval invariantsOliver Scherer-46/+37
2019-02-16Notify myself when Clippy toolstate changesPhilipp Hansch-1/+1
2019-02-16Rollup merge of #58468 - RalfJung:maybe-uninit-split, r=Centrilkennytm-33/+55
split MaybeUninit into several features, expand docs a bit This splits the `maybe_uninit` feature gate into several: * `maybe_uninit` for what we will hopefully stabilize soon-ish. * `maybe_uninit_ref` for creating references into `MaybeUninit`, for which the rules are not yet clear. * `maybe_uninit_slice` for handling slices of `MaybeUninit`, which needs more API design work. * `maybe_uninit_array` for creating arrays of `MaybeUninit` using a macro (because we don't have https://github.com/rust-lang/rust/issues/49147 yet). Is that an okay thing to do? The goal is to help people avoid APIs we do not want to stabilize yet. I used this to make sure rustc itself does not use `get_ref` and `get_mut`. I also extended the docs to advise against uninitialized integers -- again this is something for which the rules are still being discussed.
2019-02-16Rollup merge of #58448 - euclio:missing-summaries, r=QuietMisdreavuskennytm-1/+6
rustdoc: mask `compiler_builtins` docs Fixes #46783. I wasn't able to fully confirm the underlying cause, but my theory is that functions in `compiler_builtins` were overwriting functions with the same names in libcore in the search index. Since the functions in `compiler_builtins` didn't have docs, that's why they weren't appearing in the results. Masking the `compiler_builtins` crate fixes the search results. It appears that this crate was accidentally unmasked in #49503.
2019-02-16Rollup merge of #58440 - gnzlbg:v6, r=japarickennytm-0/+2
Whitelist the ARM v6 target-feature
2019-02-16Rollup merge of #58438 - cuviper:posix_spawn_file_actions_addchdir_np, ↵kennytm-2/+22
r=alexcrichton Use posix_spawn_file_actions_addchdir_np when possible This is a non-POSIX extension implemented in Solaris and in glibc 2.29. With this we can still use `posix_spawn()` when `Command::current_dir()` has been set, otherwise we fallback to `fork(); chdir(); exec()`.
2019-02-16Rollup merge of #58433 - RalfJung:miri-mark-tests, r=TimNNkennytm-79/+150
Update which libcore/liballoc tests Miri ignores, and document why
2019-02-16Rollup merge of #58429 - RalfJung:box, r=TimNNkennytm-3/+8
fix Box::into_unique effecitvely transmuting to a raw ptr Miri/Stacked Borrows treat `Box` specially: they assert that it is unique, and tag it appropriately. However, currently, `Box::into_inner` is not aware of that and returns a raw pointer (wrapped in a `Unique`) that carries the same tag as the box, meaning it carries a `Uniq` tag. This leads to all sorts of problems when people use the raw pointer they get out of the `Unique` type. In the future, it'd be interesting to make `Unique` also carry some kind of uniqueness. In that case, something like this would instead be needed whenever a raw pointer is extracted from a `Unique`. However, that is out-of-scope for the current version of Stacked Borrows. So until then, this changes `into_unique` to perform a proper reference-to-raw-ptr-cast, which clears the tag.
2019-02-16Rollup merge of #58359 - taiki-e:impl_snapshot_for, r=oli-obkkennytm-8/+6
librustc_mir: use ? in impl_snapshot_for! macro
2019-02-16Rollup merge of #58306 - GuillaumeGomez:crate-browser-history, r=QuietMisdreavuskennytm-1/+1
Don't default on std crate when manipulating browser history Fixes #58263. r? @QuietMisdreavus
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-03-01 00:49:25 +0000