about summary refs log tree commit diff
path: root/Cargo.lock
AgeCommit message (Collapse)AuthorLines
2019-04-26Update rustc-rayon versionJohn Kåre Alsaker-6/+29
2019-04-26Rollup merge of #60134 - GuillaumeGomez:fix-index-page, r=ManishearthMazdak Farrokhzad-3/+3
Fix index-page generation Fixes #60096. The minifier was minifying crates name in `searchIndex` key position, which was a bit problematic for multiple reasons. r? @rust-lang/rustdoc
2019-04-25submodules: update clippy from 9897442f to 8c0e038fMatthias Krüger-5/+7
Changes: ```` Rustup for https://github.com/rust-lang/rust/pull/59042 Update pulldown_cmark to 0.5 Only run AppVeyor on r+, try and the master branch Remove approx_constant known problems Suppress let_and_return if let has attributes Add test for or_fun_call macro suggestion UI test cleanup: Extract needless_range_loop tests Change "if types change" to "if you later change the type" ````
2019-04-23Update cargo, booksEric Huss-18/+19
2019-04-24Update hashbrown to 0.3.0Amanieu d'Antras-3/+3
2019-04-24Update hashbrown to 0.2.2Amanieu d'Antras-3/+3
2019-04-24Update hashbrown to 0.2.1Amanieu d'Antras-3/+3
2019-04-24Make libstd depend on the hashbrown crateAmanieu d'Antras-0/+19
2019-04-23Fix index-page generationGuillaume Gomez-3/+3
2019-04-22upgrade rustdoc's pulldown-cmark to 0.4.1Andy Russell-16/+31
2019-04-21Switch to serde-enabled rls-* and update RLS appropriatelyIgor Matuszewski-31/+28
This also bumps RLS version to 1.36. The updated rls-* packages use serde but *not* serde_derive thanks to manual proc macro expansion. This is a hack, since rustc cannot handle crates.io proc macros (duplicated in tools) when cross-compiling, so that's the best we can do in order to support serde_json in save-analysis.
2019-04-21save-analysis: Use serde instead of libserialize to dump JSON dataIgor Matuszewski-1/+1
2019-04-20Move almost all of cg_llvm/back/link.rs to cg_ssabjorn3-0/+1
2019-04-19submodules: update clippy from fbb3a47b to cafbe7f2Matthias Krüger-4/+4
Changes: ```` Update compiletest_rs Typo Fix dogfood error Add lint PathBufPushOverwrite Update *.stderr file Remove code duplication Format code Add test for debug_assert!(false) Don't lint debug_assert!(false) Add run-rustfix for option_map_or_none lint Move two cast_lossless tests to their correct files Change naive_bytecount applicability MaybeIncorrect Add tests for declare_lint_pass and impl_lint_pass Use lint pass macros Document `declare_lint_pass!` Fix lint_without_lint_pass internal lint Use {get,match}_def_path from LateContext Remove uplifted functions {get,match}_def_path from Clippy Add run-rustfix for len_zero lint Add run-rustfix for bool_comparison lint Add run-rustfix for deref_addrof lint while_let_loop uses placeholders in suggestions Remove rust-toolchain file from clippy_dev Update adding_lints.md Update PULL_REQUEST_TEMPLATE Add new lint checklist Create PULL_REQUEST_TEMPLATE Only suggest .copied() for Option right now Also suggest .copied() when .clone() is called on a Copy type Suggest .copied() instead of .cloned() in map_clone when dealing with references Deny rustc internal lints Remove clippy::default_hash_types internal lint Enable -Zunstable-options in .cargo/config ````
2019-04-18Update rustfmt to 1.2.1topecongiro-3/+14
2019-04-16Update cargoEric Huss-4/+4
2019-04-15Preallocate BUILTIN_ATTRIBUTES symbols and use a hash map instead of loopingJohn Kåre Alsaker-0/+2
2019-04-15Use a proc macro to declare preallocated symbolsJohn Kåre Alsaker-0/+1
2019-04-14Rollup merge of #59856 - albins:update-polonius, r=nikomatsakisMazdak Farrokhzad-4/+4
update polonius-engine This updates polonius-engine to [version 0.7.0](https://github.com/rust-lang/polonius/blob/master/RELEASES.md#v070), which adds a hybrid algorithm that starts off with performing a cheaper, location-insensitive analysis before proceeding with the full analysis. r? @nikomatsakis
2019-04-14update miriRalf Jung-0/+2
2019-04-12Use measureme in self-profilerWesley Wiser-0/+12
Related to #58372 Related to #58967
2019-04-10update polonius-engineAlbin Stjerna-4/+4
2019-04-10Update Cargo.lockJohn Kåre Alsaker-46/+46
2019-04-09update Cargo.lockMatthias Krüger-17/+5
2019-04-07Revert "Auto merge of #57842 - gnzlbg:extract_libtest, r=gnzlbg"Jacob Greenfield-17/+6
This reverts commit 3eb4890dfe6db0279fdd3cda19f9643873ae3db9, reversing changes made to 7a4df3b53da369110984a2b57419c05a53e33b38.
2019-04-04std: Upgrade `compiler_builtins` to fix wasi linkageAlex Crichton-16/+16
Turns out we needed to exclude a number of math functions on the `wasm32-unknown-wasi` target, and this was fixed in 0.1.9 of compiler-builtins and this is pulling in the fix to libstd's own build.
2019-04-04Rollup merge of #59555 - RalfJung:miri, r=oli-obkMazdak Farrokhzad-23/+1
update miri r? @oli-obk Fixes https://github.com/rust-lang/rust/issues/59477
2019-04-03Support using LLVM's libunwind as the unwinder implementationPetr Hosek-0/+1
This avoids the dependency on host libraries such as libgcc_s which may be undesirable in some deployment environments where these aren't available.
2019-04-03try to fix rand feature flagsRalf Jung-23/+1
2019-04-02Rollup merge of #59533 - Zoxc:arena-slices, r=michaelwoeristerMazdak Farrokhzad-0/+1
Support allocating iterators with arenas Split out from https://github.com/rust-lang/rust/pull/57173. r? @michaelwoerister
2019-04-02Rollup merge of #59452 - GuillaumeGomez:speedup-rustdoc, r=QuietMisdreavusMazdak Farrokhzad-3/+3
Speed up rustdoc run a bit r? @QuietMisdreavus
2019-04-01Support allocating iterators with arenasJohn Kåre Alsaker-0/+1
2019-03-30Update cargoEric Huss-12/+36
2019-03-29Add a new wasm32-unknown-wasi targetAlex Crichton-77/+77
This commit adds a new wasm32-based target distributed through rustup, supported in the standard library, and implemented in the compiler. The `wasm32-unknown-wasi` target is intended to be a WebAssembly target which matches the [WASI proposal recently announced.][LINK]. In summary the WASI target is an effort to define a standard set of syscalls for WebAssembly modules, allowing WebAssembly modules to not only be portable across architectures but also be portable across environments implementing this standard set of system calls. The wasi target in libstd is still somewhat bare bones. This PR does not fill out the filesystem, networking, threads, etc. Instead it only provides the most basic of integration with the wasi syscalls, enabling features like: * `Instant::now` and `SystemTime::now` work * `env::args` is hooked up * `env::vars` will look up environment variables * `println!` will print to standard out * `process::{exit, abort}` should be hooked up appropriately None of these APIs can work natively on the `wasm32-unknown-unknown` target, but with the assumption of the WASI set of syscalls we're able to provide implementations of these syscalls that engines can implement. Currently the primary engine implementing wasi is [wasmtime], but more will surely emerge! In terms of future development of libstd, I think this is something we'll probably want to discuss. The purpose of the WASI target is to provide a standardized set of syscalls, but it's *also* to provide a standard C sysroot for compiling C/C++ programs. This means it's intended that functions like `read` and `write` are implemented for this target with a relatively standard definition and implementation. It's unclear, therefore, how we want to expose file descriptors and how we'll want to implement system primitives. For example should `std::fs::File` have a libc-based file descriptor underneath it? The raw wasi file descriptor? We'll see! Currently these details are all intentionally hidden and things we can change over time. A `WasiFd` sample struct was added to the standard library as part of this commit, but it's not currently used. It shows how all the wasi syscalls could be ergonomically bound in Rust, and they offer a possible implementation of primitives like `std::fs::File` if we bind wasi file descriptors exactly. Apart from the standard library, there's also the matter of how this target is integrated with respect to its C standard library. The reference sysroot, for example, provides managment of standard unix file descriptors and also standard APIs like `open` (as opposed to the relative `openat` inspiration for the wasi ssycalls). Currently the standard library relies on the C sysroot symbols for operations such as environment management, process exit, and `read`/`write` of stdio fds. We want these operations in Rust to be interoperable with C if they're used in the same process. Put another way, if Rust and C are linked into the same WebAssembly binary they should work together, but that requires that the same C standard library is used. We also, however, want the `wasm32-unknown-wasi` target to be usable-by-default with the Rust compiler without requiring a separate toolchain to get downloaded and configured. With that in mind, there's two modes of operation for the `wasm32-unknown-wasi` target: 1. By default the C standard library is statically provided inside of `liblibc.rlib` distributed as part of the sysroot. This means that you can `rustc foo.wasm --target wasm32-unknown-unknown` and you're good to go, a fully workable wasi binary pops out. This is incompatible with linking in C code, however, which may be compiled against a different sysroot than the Rust code was previously compiled against. In this mode the default of `rust-lld` is used to link binaries. 2. For linking with C code, the `-C target-feature=-crt-static` flag needs to be passed. This takes inspiration from the musl target for this flag, but the idea is that you're no longer using the provided static C runtime, but rather one will be provided externally. This flag is intended to also get coupled with an external `clang` compiler configured with its own sysroot. Therefore you'll typically use this flag with `-C linker=/path/to/clang-script-wrapper`. Using this mode the Rust code will continue to reference standard C symbols, but the definition will be pulled in by the linker configured. Alright so that's all the current state of this PR. I suspect we'll definitely want to discuss this before landing of course! This PR is coupled with libc changes as well which I'll be posting shortly. [LINK]: [wasmtime]:
2019-03-29Rollup merge of #59454 - topecongiro:rustfmt-1.2.0, r=nrcMazdak Farrokhzad-2/+2
Update rustfmt to 1.2.0 This release includes bug fixes and performance improvements from 1.1.0. Also it adds a new rustfmt tool attribute `#[rustfmt::skip::macros]`, which lets you skip formatting macro calls of your choice. cc @nrc @Centril @Xanewok
2019-03-29Rollup merge of #59436 - gnzlbg:update_jemalloc, r=alexcrichtonMazdak Farrokhzad-6/+6
Update jemalloc-sys to version 0.3.0 This PR updates jemalloc-sys from 0.1.8 to 0.3.0.
2019-03-27Speed up rustdoc run a bitGuillaume Gomez-6/+6
2019-03-27Update ena to version 0.13.0varkor-3/+3
2019-03-27Update enavarkor-1/+10
2019-03-27Update rustfmt to 1.2.0topecongiro-5/+5
2019-03-26Update Cargo.lockgnzlbg-6/+6
2019-03-26Rollup merge of #59315 - Zoxc:move-query, r=oli-obkMazdak Farrokhzad-0/+1
Add no_hash to query macro and move some queries over r? @oli-obk
2019-03-21Update cargoMikaelUrankar-64/+64
2019-03-20Add no_hash to query macro and move some queries overJohn Kåre Alsaker-0/+1
2019-03-19Directly reference the roadmap upstreamgnzlbg-7/+18
2019-03-19Update Cargo.lockgnzlbg-1/+1
2019-03-18Update Clippy, RLS and RustfmtMateusz Mikuła-78/+52
2019-03-16Remove MetadataOnlyCodegenBackendbjorn3-1/+0
2019-03-13Update cargoEric Huss-3/+3
2019-03-13Rollup merge of #58908 - JohnTitor:improve-rand, r=scottmcmMazdak Farrokhzad-1/+1
Update rand version cc: #57724 r? @scottmcm