rust - https://github.com/rust-lang/rust

Age	Commit message (Collapse)	Author	Lines
2022-02-27	expadn abi check + condese & fix tests	DrMeepster	-7/+2

2022-02-27	fix box icing when it has aggregate abi	DrMeepster	-0/+22

2022-02-15	fix assumption that ScalarPair Box is always a fat pointer	DrMeepster	-0/+6

2021-11-20	Point at source of trait bound obligations in more places	Esteban Kuber	-6/+6
	Be more thorough in using `ItemObligation` and `BindingObligation` when evaluating obligations so that we can point at trait bounds that introduced unfulfilled obligations. We no longer incorrectly point at unrelated trait bounds (`substs-ppaux.verbose.stderr`). In particular, we now point at trait bounds on method calls. We no longer point at "obvious" obligation sources (we no longer have a note pointing at `Trait` saying "required by a bound in `Trait`", like in `associated-types-no-suitable-supertrait*`). Address part of #89418.
2021-11-14	Move some tests to more reasonable directories	Caio	-0/+27

2021-11-06	Move some tests to more reasonable directories	Caio	-0/+30

2021-09-25	Use larger span for adjustments on method calls	Aaron Hill	-1/+1
	Currently, we use a relatively 'small' span for THIR expressions generated by an 'adjustment' (e.g. an autoderef, autoborrow, unsizing). As a result, if a borrow generated by an adustment ends up causing a borrowcheck error, for example: ```rust let mut my_var = String::new(); let my_ref = &my_var my_var.push('a'); my_ref; ``` then the span for the mutable borrow may end up referring to only the base expression (e.g. `my_var`), rather than the method call which triggered the mutable borrow (e.g. `my_var.push('a')`) Due to a quirk of the MIR borrowck implementation, this doesn't always get exposed in migration mode, but it does in many cases. This commit makes THIR building consistently use 'larger' spans for adjustment expressions The intent of this change it make it clearer to users when it's the specific way in which a variable is used (for example, in a method call) that produdes a borrowcheck error. For example, an error message claiming that a 'mutable borrow occurs here' might be confusing if it just points at a usage of a variable (e.g. `my_var`), when no `&mut` is in sight. Pointing at the entire expression should help to emphasize that the method call itself is responsible for the mutable borrow. In several cases, this makes the `#![feature(nll)]` diagnostic output match up exactly with the default (migration mode) output. As a result, several `.nll.stderr` files end up getting removed entirely.
2021-09-16	Point at call span that introduced obligation for the arg	Esteban Kuber	-2/+6

2021-07-19	Various diagnostics clean ups/tweaks	Esteban Küber	-2/+10
	* Always point at macros, including derive macros * Point at non-local items that introduce a trait requirement * On private associated item, point at definition
2020-12-04	Rename `AllocRef` to `Allocator` and `(de)alloc` to `(de)allocate`	Tim Diekmann	-8/+8

2020-10-07	Support custom allocators in `Box`	Tim Diekmann	-0/+140
	Remove `Box::leak_with_alloc` Add leak-test for box with allocator Rename `AllocErr` to `AllocError` in leak-test Add `Box::alloc` and adjust examples to use the new API