https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=master 2019-12-30T16:18:16+00:00 2019-12-30T16:18:16+00:00 Vadim Petrochenkov vadim.petrochenkov@gmail.com 2019-12-29T13:39:31+00:00 urn:sha1:b683de4ad79242fdeebcae2afefb72c1530babe9 `syntax_expand` -> `rustc_expand` `syntax_pos` -> `rustc_span` `syntax_ext` -> `rustc_builtin_macros` 2019-12-29T04:30:56+00:00 bors bors@rust-lang.org 2019-12-29T04:30:56+00:00 urn:sha1:774a4bd4f4f6c91dda7c46550769349a522856f7 Set callbacks globally This sets the callbacks from syntax and rustc_errors just once, utilizing static (rather than thread-local) storage. 2019-12-27T19:56:11+00:00 Sean McArthur sean@seanmonstar.com 2019-12-26T20:57:09+00:00 urn:sha1:f35517ee861dc012ccc26083dd4520045e2c4f6f 2019-12-25T19:10:46+00:00 Mark Rousskov mark.simulacrum@gmail.com 2019-12-25T18:38:57+00:00 urn:sha1:b98633b94c5354fbcb02bd0111f2aba5155c3190 The callbacks have precisely two states: the default, and the one present throughout almost all of the rustc run (the filled in value which has access to TyCtxt). We used to store this as a thread local, and reset it on each thread to the non-default value. But this is somewhat wasteful, since there is no reason to set it globally -- while the callbacks themselves access TLS, they do not do so in a manner that fails in when we do not have TLS to work with. 2019-12-25T06:39:49+00:00 David Tolnay dtolnay@gmail.com 2019-12-01T04:01:48+00:00 urn:sha1:4646a88b7a1e68326d092b9cbbbbdd616a51077f `description` has been documented as soft-deprecated since 1.27.0 (17 months ago). There is no longer any reason to call it or implement it. This commit: - adds #[rustc_deprecated(since = "1.41.0")] to Error::description; - moves description (and cause, which is also deprecated) below the source and backtrace methods in the Error trait; - reduces documentation of description and cause to take up much less vertical real estate in rustdocs, while preserving the example that shows how to render errors without needing to call description; - removes the description function of all *currently unstable* Error impls in the standard library; - marks #[allow(deprecated)] the description function of all *stable* Error impls in the standard library; - replaces miscellaneous uses of description in example code and the compiler. 2019-12-23T13:47:19+00:00 Mazdak Farrokhzad twingoow@gmail.com 2019-11-11T10:39:52+00:00 urn:sha1:5f92a56ed69d9384429353b713d74f67ee8f957c Under the gate, `x @ Some(y)` is allowed. This is subject to various restrictions for soundness. 2019-12-22T22:42:47+00:00 Mark Rousskov mark.simulacrum@gmail.com 2019-12-22T22:42:04+00:00 urn:sha1:a06baa56b95674fc626b3c3fd680d6a65357fe60 2019-12-20T21:53:40+00:00 Mazdak Farrokhzad twingoow@gmail.com 2019-12-03T17:08:19+00:00 urn:sha1:c9e1f13f6eb9d21224c083eb07d894adffc7ec96 2019-12-15T01:28:28+00:00 bors bors@rust-lang.org 2019-12-15T01:28:28+00:00 urn:sha1:fc6b5d6efe163060bde31cc1c801086ed7ebc8f1 Enable `loop` and `while` in constants behind a feature flag This PR is an initial implementation of #52000. It adds a `const_loop` feature gate, which allows `while` and `loop` expressions through both HIR and MIR const-checkers if enabled. `for` expressions remain forbidden by the HIR const-checker, since they desugar to a call to `IntoIterator::into_iter`, which will be rejected anyways. `while` loops also require [`#![feature(const_if_match)]`](https://github.com/rust-lang/rust/pull/66507), since they have a conditional built into them. The diagnostics from the HIR const checker will suggest this to the user. r? @oli-obk cc @rust-lang/wg-const-eval 2019-12-13T18:38:29+00:00 Dylan MacKenzie ecstaticmorse@gmail.com 2019-12-10T20:41:58+00:00 urn:sha1:57959b2bdcd047745f3b403c25cc470c9a0889d9