about summary refs log tree commit diff
path: root/tests/ui/rfc-2632-const-trait-impl
AgeCommit message (Collapse)AuthorLines
2023-06-05Better group RFC ui tests togetherMaybe Waffle-3555/+0
2023-05-05Disallow (min) specialization imps with no itemsMatthew Jasper-20/+56
Such implementations are usually mistakes and are not used in the compiler or standard library (after this commit) so forbid them with `min_specialization`.
2023-05-01Don't use implied trait predicates in gather_explicit_predicates_ofMichael Goulet-10/+36
2023-04-19Auto merge of #110393 - fee1-dead-contrib:rm-const-traits, r=oli-obkbors-197/+432
Rm const traits in libcore See [zulip thread](https://rust-lang.zulipchat.com/#narrow/stream/146212-t-compiler.2Fconst-eval/topic/.60const.20Trait.60.20removal.20or.20rework) * [x] Bless ui tests * [ ] Re constify some unstable functions with workarounds if they are needed
2023-04-16fix library and rustdoc testsDeadbeef-197/+432
2023-04-16Rollup merge of #109665 - fee1-dead-contrib:rm-remap-queries, r=oli-obkfee1-dead-0/+23
Remove `remap_env_constness` in queries This removes some of the complexities with const traits. #88119 used to be caused by this but was fixed by `param_env = param_env.without_const()`.
2023-04-12Tweak output for 'add line' suggestionEsteban Küber-1/+2
2023-04-08fix ICEDeadbeef-0/+23
2023-03-29Stabilize a portion of 'once_cell'Trevor Gross-1/+1
Move items not part of this stabilization to 'lazy_cell' or 'once_cell_try'
2023-03-28fix long lineDeadbeef-23/+25
2023-03-28Move const trait bounds checks to MIR constckDeadbeef-220/+276
Fixes #109543. When checking paths in HIR typeck, we don't want to check for const predicates since all we want might just be a function pointer. Therefore we move this to MIR constck and check that bounds are met during MIR constck.
2023-03-11Gate const closures even when they appear in macrosMichael Goulet-3/+20
2023-02-24Rollup merge of #106541 - fee1-dead-contrib:no-const-check-no, r=thomccDylan DPC-0/+37
implement const iterator using `rustc_do_not_const_check` Previous experiment: #102225. Explanation: rather than making all default methods work under `const` all at once, this uses `rustc_do_not_const_check` as a workaround to "trick" the compiler to not run any checks on those other default methods. Any const implementations are only required to implement the `next` method. Any actual calls to the trait methods other than `next` will either error in compile time (at CTFE runs), or run the methods correctly if they do not have any non-const operations. This is extremely easy to maintain, remove, or improve.
2023-02-07Add ~const bounds trait bounds when using derive_constMichael Goulet-0/+13
2023-02-01fix parser mistaking const closures for const itemDeadbeef-0/+10
2023-01-31add and bless testsDeadbeef-0/+19
2023-01-31implement const iterator using `rustc_do_not_const_check`Deadbeef-0/+18
2023-01-13Rollup merge of #106785 - compiler-errors:better-impl-wf-spans, r=estebankYuki Okushi-4/+4
Make blame spans better for impl wfcheck r? types
2023-01-12Point at impl self type for impl wf obligationsMichael Goulet-4/+4
2023-01-12move to correct testDeadbeef-0/+53
2023-01-12fix fmt and blessDeadbeef-0/+4
2023-01-11Note predicate span on ImplDerivedObligationMichael Goulet-1/+3
2023-01-11Move /src/test to /testsAlbert Larsan-0/+3040