- 06 12月, 2019 30 次提交
-
-
由 varkor 提交于
-
由 varkor 提交于
-
由 varkor 提交于
-
由 bors 提交于
Rollup of 10 pull requests Successful merges: - #66649 (VxWorks: fix issues in accessing environment variables) - #66764 (Tweak wording of `collect()` on bad target type) - #66900 (Clean up error codes) - #66974 ([CI] fix the `! isCI` check in src/ci/run.sh) - #66979 (Add long error for E0631 and update ui tests.) - #67017 (cleanup long error explanations) - #67021 (Fix docs for formatting delegations) - #67041 (add ExitStatusExt into prelude) - #67065 (Fix fetching arguments on the wasm32-wasi target) - #67066 (Update the revision of wasi-libc used in wasm32-wasi) Failed merges: r? @ghost
-
由 Yuki Okushi 提交于
Update the revision of wasi-libc used in wasm32-wasi This commit updates the `wasi-libc` repository used to build the wasm32-wasi target's libstd to ensure that both libstd and libc are using the same wasi snapshot version.
-
由 Yuki Okushi 提交于
Fix fetching arguments on the wasm32-wasi target Fixes an error introduced in #66750 where wasi executables always think they have zero arguments because one of the vectors returned here accidentally thought it was length 0.
-
由 Yuki Okushi 提交于
add ExitStatusExt into prelude r? @alexcrichton
-
由 Yuki Okushi 提交于
Fix docs for formatting delegations If you use the example in the docs right now it breaks all the options Formatters have to offer. i.e. https://play.rust-lang.org/?version=stable&mode=debug&edition=2018&gist=214392ecc6eff73b4789c32568395f72 this should've padded the output with 4 zeros but didn't. with the new example it does work: https://play.rust-lang.org/?version=stable&mode=debug&edition=2018&gist=3bdfb29f395230c5129c5f56dcfcb2a9 The only thing i'm not quite sure about is what's the right way to do it in a loop (altough non of the docs talk about it people are doing it in the wild and there were a couple of attempts to include in libcore) i.e. https://play.rust-lang.org/?version=stable&mode=debug&edition=2018&gist=4c4dca3c90ba36779ecd014f3899ab9c
-
由 Yuki Okushi 提交于
cleanup long error explanations r? @Dylan-DPC
-
由 Yuki Okushi 提交于
Add long error for E0631 and update ui tests. This PR adds a long error for `E0631`, which covers errors where closure argument types are mismatched. It also updates UI tests where this error is applicable. Part of #61137
-
由 Yuki Okushi 提交于
[CI] fix the `! isCI` check in src/ci/run.sh Using `if [ ! isCI ] || ...` doesn't run any command, just tests `isCI` as a string, whereas `if ! isCI || ...` will actually run the `isCI` command and negate its exit status.
-
由 Yuki Okushi 提交于
Clean up error codes r? @Dylan-DPC
-
由 Yuki Okushi 提交于
Tweak wording of `collect()` on bad target type Fix #60440.
-
由 Yuki Okushi 提交于
VxWorks: fix issues in accessing environment variables
-
由 bors 提交于
std:win: avoid WSA_FLAG_NO_INHERIT flag and don't use SetHandleInformation on UWP This flag is not supported on Windows 7 before SP1, and on windows server 2008 SP2. This breaks Socket creation & duplication. This was fixed in a previous PR. cc #26658 This PR: cc #60260 reuses this flag to support UWP, and makes an attempt to handle the potential error. This version still fails to create a socket, as the error returned by WSA on this case is WSAEINVAL (invalid argument). and not WSAEPROTOTYPE. MSDN page for WSASocketW (that states the platform support for WSA_FLAG_NO_HANDLE_INHERIT): https://docs.microsoft.com/en-us/windows/win32/api/winsock2/nf-winsock2-wsasocketw CC #26543 CC #26518
-
由 bors 提交于
rustc_mir: use nicer path printing for #[rustc_regions] NLL tests. Similar to #66850, spotted while working on #66907. r? @matthewjasper
-
由 bors 提交于
Rollup of 9 pull requests Successful merges: - #66710 (weak-into-raw: Clarify some details in Safety) - #66863 (Check break target availability when checking breaks with values) - #67002 (Fix documentation of pattern for str::matches()) - #67005 (capitalize Rust) - #67010 (Accurately portray raw identifiers in error messages) - #67011 (Include a span in more `expected...found` notes) - #67044 (E0023: handle expected != tuple pattern type) - #67045 (rustc_parser: cleanup imports) - #67055 (Make const-qualification look at more `const fn`s) Failed merges: r? @ghost
-
由 Alex Crichton 提交于
This commit updates the `wasi-libc` repository used to build the wasm32-wasi target's libstd to ensure that both libstd and libc are using the same wasi snapshot version.
-
由 Alex Crichton 提交于
Fixes an error introduced in #66750 where wasi executables always think they have zero arguments because one of the vectors returned here accidentally thought it was length 0.
-
由 Mazdak Farrokhzad 提交于
Make const-qualification look at more `const fn`s As explained in a lot more detail in #67053 this makes const-qualification not ignore the unstable const fns in libcore. r? @oli-obk cc @ecstatic-morse (Still a bit unsure about the `cfg`s here, for bootstrapping, does that seem correct ?) Fixes #67053.
-
由 Mazdak Farrokhzad 提交于
rustc_parser: cleanup imports Reorganize & canonicalize some imports + Drop `rustc_target` as a dependency. r? @Mark-Simulacrum
-
由 Mazdak Farrokhzad 提交于
E0023: handle expected != tuple pattern type Fixes #67037. r? @estebank
-
由 Mazdak Farrokhzad 提交于
Include a span in more `expected...found` notes In most places, we use a span when emitting `expected...found` errors. However, there were a couple of places where we didn't use any span, resulting in hard-to-interpret error messages. This commit attaches the relevant span to these notes, and additionally switches over to using `note_expected_found` instead of manually formatting the message
-
由 Mazdak Farrokhzad 提交于
Accurately portray raw identifiers in error messages When refering to or suggesting raw identifiers, refer to them with `r#`. Fix #65634.
-
由 Mazdak Farrokhzad 提交于
capitalize Rust Capitalize "Rust" in docs.
-
由 Mazdak Farrokhzad 提交于
Fix documentation of pattern for str::matches() Made it the same as rmatches()
-
由 Mazdak Farrokhzad 提交于
Check break target availability when checking breaks with values Fixes #66702 I'll be adding a regression test.
-
由 Mazdak Farrokhzad 提交于
weak-into-raw: Clarify some details in Safety Clarify it is OK to pass a pointer that never owned a weak count (one from Weak::new) back into it as it was created from it. Relates to discussion in #60728. @CAD97 Do you want to have a look at the new docs?
-
由 bors 提交于
Less minification The goal of this PR is to remove the minification process on the `search-index.js` file. It provides great result in term of space reduction but the computation time is far too long. I'll work on this issue and will put it back once it's fast enough. cc @nox @lqd r? @kinnison
-
由 Remy Rakic 提交于
-
- 05 12月, 2019 10 次提交
-
-
由 bors 提交于
Reorganize borrow check diagnostic code Currently borrow checker diagnostics are split across many different modules in different places in the `librustc_mir` crate. This moves them all to a `diagnostics` module. This also reduces the nesting of the modules a bit (sooo much nesting). I am also thinking of moving stuff out of the `nll` module since we only have one borrow checker now (
🎉 ), and maybe it even makes sense to split out all of this stuff to a `librustc_borrow_check`, but those are for the future. Feel free to ping me here or on zulip and let me know what you think... cc @nikomatsakis @matthewjasper @EddyB -
由 Michal 'vorner' Vaner 提交于
Clarify it is OK to pass a pointer that never owned a weak count (one from Weak::new) back into it as it was created from it. Relates to discussion in #60728.
-
由 Remy Rakic 提交于
-
由 Remy Rakic 提交于
So that we can bootstrap successfully
-
由 Remy Rakic 提交于
the unstables ones in libcore, with the unstable feature disabled, were not checked
-
由 bors 提交于
Use Module::print() instead of a PrintModulePass llvm::Module has a print() method. It is unnecessary to create a pass just for the purpose of printing LLVM IR.
-
由 Mazdak Farrokhzad 提交于
-
由 bors 提交于
Disable gdb pretty printer global section on wasm targets The wasm targets don't support gdb anyway so there's no need for this section there.
-
由 Mazdak Farrokhzad 提交于
-
由 Alex Crichton 提交于
The wasm targets don't support gdb anyway so there's no need for this section there.
-