about summary refs log tree commit diff
path: root/src/libsyntax/parse
diff options
context:
space:
mode:
authorbors <bors@rust-lang.org>2018-10-13 17:03:47 +0000
committerbors <bors@rust-lang.org>2018-10-13 17:03:47 +0000
commit8f19cadf9508963ca3af9c9b184b65f4e0ff70e4 (patch)
tree242066196644b61c9954b379ea1a07bcf0ab4048 /src/libsyntax/parse
parentf51752774bbbe48d2aabe53c86e9e91ed3a73a5d (diff)
parentab91a6b4df04a60cf19682b1f016848d3e4784ad (diff)
downloadrust-8f19cadf9508963ca3af9c9b184b65f4e0ff70e4.tar.gz
rust-8f19cadf9508963ca3af9c9b184b65f4e0ff70e4.zip
Auto merge of #55003 - zackmdavis:must_use_assoc_fn, r=varkor
`#[must_use]` for associated functions is supposed to actually work

In the comments of (closed, defunct) pull request #54884, @Centril [noted that](https://github.com/rust-lang/rust/pull/54884#issuecomment-427626495) 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.)

r? @varkor
Diffstat (limited to 'src/libsyntax/parse')
0 files changed, 0 insertions, 0 deletions