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

Age	Commit message (Collapse)	Author	Lines
2018-07-25	Deny bare_trait_objects globally	Tatsuyuki Ishi	-2/+0

2018-07-24	Use suggestions for `printf` format	Esteban Küber	-5/+66

2018-07-24	Rollup merge of #52658 - Wallacoloo:topics/use-option-methods, r=cramertj	Mark Rousskov	-8/+4
	Prefer `Option::map`/etc over `match` wherever it improves clarity This isn't intended to change behavior anywhere. A lot of times statements like `match x { None => None, Some(y) => [...] }` can be rewritten using `Option::map` or `Option::and_then` in a way that preserves or improves clarity, so that's what I've done here. I think it's particularly valuable to keep things in `libcore` and `libstd` pretty/idiomatic since it's not uncommon to follow the `[src]` links when browsing the rust-lang.org docs for std/core. If there's any concern about pushing style-based changes though, I'll happily back out the non-std/core commits here.
2018-07-24	Reword missing formatting arguments label	Esteban Küber	-1/+1

2018-07-23	libsyntax_ext: Prefer `Option::map` over `match` where applicable	Colin Wallace	-8/+4

2018-07-23	Only point at inside of string literals if they're actually string literals	Esteban Küber	-6/+24

2018-07-23	Point only at invalid positional arguments	Esteban Küber	-62/+76

2018-07-23	Point at incorrect named arg in format string	Esteban Küber	-2/+19

2018-07-23	Replace a few expect+format combos with unwrap_or_else+panic	ljedrz	-2/+2

2018-07-22	Point at internal span in format string	Esteban Küber	-12/+22

2018-07-21	fix logic bug	Esteban Küber	-2/+2

2018-07-21	Remove dependency on `libsyntax`	Esteban Küber	-1/+5

2018-07-21	Gate `format_args_nll` behind feature flag	Esteban Küber	-0/+15

2018-07-21	Suggest space separated format str literal	Esteban Küber	-1/+1

2018-07-19	Use correct spans for format string errors	Esteban Küber	-1/+1
	When encountering format string errors in a raw string, or regular string literal with embedded newlines, account for the positional change to use correct spans. :drive by fix: 🚗
2018-07-19	rework println	Esteban Küber	-2/+30

2018-07-19	review comments: modify note wording and change `println`	Esteban Küber	-1/+1
	- Don't print the newline on its own to avoid the possibility of printing it out of order due to `stdout` locking. - Modify wording of `concat!()` with non-literals to not mislead into believing that only `&str` literals are accepted. - Add test for `concat!()` with non-literals.
2018-07-19	Improve suggestion for missing fmt str in println	Esteban Küber	-14/+29
	Avoid using `concat!(fmt, "\n")` to improve the diagnostics being emitted when the first `println!()` argument isn't a formatting string literal.
2018-07-15	Auto merge of #52383 - petrochenkov:pmns, r=alexcrichton	bors	-5/+0
	resolve: Functions introducing procedural macros reserve a slot in the macro namespace as well Similarly to https://github.com/rust-lang/rust/pull/52234, this gives us symmetry between internal and external views of a crate, but in this case it's always an error to call a procedural macro in the same crate in which it's defined. Closes https://github.com/rust-lang/rust/issues/52225
2018-07-14	Auto merge of #52326 - alexcrichton:tweak-proc-macro-expand, r=petrochenkov	bors	-3/+8
	rustc: Tweak expansion of #[proc_macro] for 2018 The syntactical expansion of `#[proc_macro]` and related attributes currently contains absolute paths which conflicts with a lint for the 2018 edition, causing issues like #52214. This commit puts a band-aid on the issue by ensuring that procedural macros can also migrate to the 2018 edition for now by tweaking the expansion based on what features are activated. A more long-term solution would probably tweak the edition hygiene of spans, but this should do the trick for now. Closes #52214
2018-07-14	Functions introducing procedural macros reserve a slot in the macro ↵	Vadim Petrochenkov	-5/+0
	namespace as well
2018-07-14	Address comments	Vadim Petrochenkov	-6/+4

2018-07-14	Remove some tests using AST comparisons, fix other tests	Vadim Petrochenkov	-4/+4

2018-07-14	Remove most of `PartialEq` impls from AST and HIR structures	Vadim Petrochenkov	-20/+16

2018-07-13	rustc: Tweak expansion of #[proc_macro] for 2018	Alex Crichton	-3/+8
	The syntactical expansion of `#[proc_macro]` and related attributes currently contains absolute paths which conflicts with a lint for the 2018 edition, causing issues like #52214. This commit puts a band-aid on the issue by ensuring that procedural macros can also migrate to the 2018 edition for now by tweaking the expansion based on what features are activated. A more long-term solution would probably tweak the edition hygiene of spans, but this should do the trick for now. Closes #52214
2018-07-13	proc_macro: Fix crate root detection	Vadim Petrochenkov	-10/+6

2018-07-12	Rollup merge of #52295 - ljedrz:dyn_libsyntax_ext, r=petrochenkov	kennytm	-35/+37
	Deny bare trait objects in src/libsyntax_ext Enforce `#![deny(bare_trait_objects)]` in `src/libsyntax_ext`.
2018-07-12	Rollup merge of #52276 - alexcrichton:validate-proc-macro-attr, r=petrochenkov	kennytm	-4/+4
	rustc: Verify #[proc_macro] is only a word ... and perform the same verification for #[proc_macro_attribute], currently neither of these attributes take any arguments. Closes #52273
2018-07-12	Deny bare trait objects in src/libsyntax_ext	ljedrz	-35/+37

2018-07-11	rustc: Verify #[proc_macro] is only a word	Alex Crichton	-4/+4
	... and perform the same verification for #[proc_macro_attribute], currently neither of these attributes take any arguments. Closes #52273
2018-07-11	suggest on new snippet	csmoe	-29/+29

2018-07-06	suggests with whole macro call	csmoe	-10/+1

2018-07-04	add span note	csmoe	-1/+8

2018-07-03	Suggestion for print	csmoe	-1/+8

2018-06-27	Implement `#[macro_export(local_inner_macros)]`	Vadim Petrochenkov	-0/+3

2018-06-26	migrate codebase to `..=` inclusive range patterns	Zack M. Davis	-7/+7
	These were stabilized in March 2018's #47813, and are the Preferred Way to Do It going forward (q.v. #51043).
2018-06-23	hygiene: Merge `NameAndSpan` into `ExpnInfo`	Vadim Petrochenkov	-10/+8

2018-06-21	Parse async fn header.	Without Boats	-5/+5
	This is gated on edition 2018 & the `async_await` feature gate. The parser will accept `async fn` and `async unsafe fn` as fn items. Along the same lines as `const fn`, only `async unsafe fn` is permitted, not `unsafe async fn`.The parser will not accept `async` functions as trait methods. To do a little code clean up, four fields of the function type struct have been merged into the new `FnHeader` struct: constness, asyncness, unsafety, and ABI. Also, a small bug in HIR printing is fixed: it previously printed `const unsafe fn` as `unsafe const fn`, which is grammatically incorrect.
2018-06-20	Fix additional comments	varkor	-1/+1

2018-06-20	Rename ty_param_bound to trait_bound	varkor	-5/+5

2018-06-20	Rename ParamBound(s) to GenericBound(s)	varkor	-2/+2

2018-06-20	Remove name from GenericParamKind::Lifetime	varkor	-4/+4

2018-06-20	Lift bounds into GenericParam	varkor	-12/+10

2018-06-20	Simply joint lifetime/type iteration	varkor	-58/+22

2018-06-20	Rename structures in ast	varkor	-26/+26

2018-06-20	Remove all traces of lifetimes() and types() methods	varkor	-23/+21

2018-06-20	Remove methods from ast::GenericParam and ast::Generics	varkor	-2/+8

2018-06-20	Refactor ast::GenericParam as a struct	varkor	-31/+29

2018-06-20	Refactor hir::GenericParam as a struct	varkor	-3/+7

2018-06-20	Rename ast::GenericParam and ast::GenericArg	varkor	-27/+27
	It's so confusing to have everything having the same name, at least while refactoring.