about summary refs log tree commit diff
path: root/src/test/ui/fn_must_use.stderr
AgeCommit message (Collapse)AuthorLines
2021-03-20Move some tests to more reasonable directories - 5Caio-59/+0
2020-04-11rustc: Add a warning count upon completionRoccoDev-0/+2
2020-01-24Normalise notes with the/isvarkor-1/+1
2019-03-11Update testsVadim Petrochenkov-6/+6
2018-12-25Remove licensesMark Rousskov-9/+9
2018-10-14Unused result warning: "X which must" ↦ "X that must"varkor-8/+8
2018-10-12`#[must_use]` for associated functions is supposed to actually workZack M. Davis-7/+13
In the comments of (closed, defunct) pull request #54884, Mazdak "Centril" Farrokhzad noted that must-use annotations didn't work on an associated function (what other communities might call a "static method"). Subsequent logging revealed that in this case we have a `Def::Method`, whereas the lint pass was only matching on `Def::Fn`. (One could argue that those def-names are thereby misleading—must-use for self-ful methods have always worked—but documenting or reworking that can be left to another day.)
2018-05-06in which the must-use additional messaging is tucked into a noteZack M. Davis-2/+5
Also, a comment is edited to reflect that spaces around the equals-sign in attributes is the standard (q.v. rust-lang-nursery/fmt-rfcs@bea80532e7).
2018-04-28stabilize `#[must_use]` for functions and must-use operatorsZack M. Davis-0/+48
This is in the matter of RFC 1940 and tracking issue #43302.