rust/src/librustc/traits/query, branch try-perfhttps://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=try-perf2020-02-16T10:41:25+00:00Move librustc/{traits,infer} to librustc_infer.2020-02-16T10:41:25+00:00Camille GILLOTgillot.camille@gmail.com2020-01-06T19:13:24+00:00urn:sha1:d5691209b6d5fe5e47560b1db7b822dbeb0880fdMove traits::query datatypes to traits::types.2020-02-05T07:45:09+00:00Camille GILLOTgillot.camille@gmail.com2020-01-22T08:04:50+00:00urn:sha1:4e42f388c375b0d6eb25af087cb2a66069419529Add an early-exit to `QueryNormalizer::fold_ty`2020-01-28T16:28:19+00:00Jonas Schievinkjonasschievink@gmail.com2020-01-27T23:52:21+00:00urn:sha1:474d0e33717062696be4c9799ce9822bf7b56fc2Rollup merge of #68140 - ecstatic-morse:const-trait-bound-opt-out, r=oli-obk2020-01-21T18:42:20+00:00Mazdak Farrokhzadtwingoow@gmail.com2020-01-21T18:42:20+00:00urn:sha1:3484e2fab4153068e4e5eaebab215e680efe38f1
Implement `?const` opt-out for trait bounds
For now, such bounds are treated exactly the same as unprefixed ones in all contexts. [RFC 2632](https://github.com/rust-lang/rfcs/pull/2632) does not specify whether such bounds are forbidden outside of `const` contexts, so they are allowed at the moment.
Prior to this PR, the constness of a trait bound/impl was stored in `TraitRef`. Now, the constness of an `impl` is stored in `ast::ItemKind::Impl` and the constness of a bound in `ast::TraitBoundModifer`. Additionally, constness of trait bounds is now stored in an additional field of `ty::Predicate::Trait`, and the combination of the constness of the item along with any `TraitBoundModifier` determines the constness of the bound in accordance with the RFC. Encoding the constness of impls at the `ty` level is left for a later PR.
After a discussion in \#wg-grammar on Discord, it was decided that the grammar should not encode the mutual exclusivity of trait bound modifiers. The grammar for trait bound modifiers remains `[?const] [?]`. To encode this, I add a dummy variant to `ast::TraitBoundModifier` that is used when the syntax `?const ?` appears. This variant causes an error in AST validation and disappears during HIR lowering.
cc #67794
r? @oli-obk
Add `constness` field to `ty::Predicate::Trait`2020-01-20T08:00:08+00:00Dylan MacKenzieecstaticmorse@gmail.com2020-01-14T04:30:31+00:00urn:sha1:ab3081a70e5d402188c26c6f3e671a3c44812d1bremove rustc_error_codes deps except in rustc_driver2020-01-18T20:53:53+00:00Mazdak Farrokhzadtwingoow@gmail.com2020-01-18T20:53:53+00:00urn:sha1:de6046fa0ff6e57afa50174c001d1668ee7f3cf6nix syntax::errors & prefer rustc_errors over errors2020-01-10T06:41:30+00:00Mazdak Farrokhzadtwingoow@gmail.com2020-01-09T10:18:47+00:00urn:sha1:8bd3d240e3fbfe5ad39585faef1fcfb4ae42ac59- remove syntax::{span_warn!, span_err!, span_fatal!. struct_err!}2020-01-08T03:25:33+00:00Mazdak Farrokhzadtwingoow@gmail.com2019-12-31T20:25:16+00:00urn:sha1:2c3e5d3de023c0bfbf4a4c4d3b0d7a9844e96ffe
- remove syntax::{help!, span_help!, span_note!}
- remove unused syntax::{struct_span_fatal, struct_span_err_or_warn!, span_err_or_warn!}
- lintify check_for_bindings_named_same_as_variants + conflicting_repr_hints
- inline syntax::{struct_span_warn!, diagnostic_used!}
- stringify_error_code! -> error_code! & use it more.
- find_plugin_registrar: de-fatalize an error
- de-fatalize metadata errors
- move type_error_struct! to rustc_typeck
- struct_span_err! -> rustc_errors
Move normalize_erasing_regions to rustc::ty.2020-01-07T16:46:23+00:00Camille GILLOTgillot.camille@gmail.com2020-01-05T18:43:25+00:00urn:sha1:a80bff87c19cf91deafefc8fdaace71f77727258Remove rustc_hir reexports in rustc::hir.2020-01-05T11:49:22+00:00Mazdak Farrokhzadtwingoow@gmail.com2020-01-05T01:37:57+00:00urn:sha1:ebfd8673a791661d9cb526d9994f2f6bbfa49348