153 lines
4.9 KiB
Rust
Executable File
153 lines
4.9 KiB
Rust
Executable File
//! This file tests for the DOC_MARKDOWN lint
|
||
//~^ ERROR: you should put `DOC_MARKDOWN` between ticks
|
||
|
||
#![feature(plugin)]
|
||
#![plugin(clippy)]
|
||
|
||
#![deny(doc_markdown)]
|
||
|
||
/// The foo_bar function does _nothing_. See also foo::bar. (note the dot there)
|
||
//~^ ERROR: you should put `foo_bar` between ticks
|
||
//~| ERROR: you should put `foo::bar` between ticks
|
||
/// Markdown is _weird_. I mean _really weird_. This \_ is ok. So is `_`. But not Foo::some_fun
|
||
//~^ ERROR: you should put `Foo::some_fun` between ticks
|
||
/// which should be reported only once despite being __doubly bad__.
|
||
/// Here be ::is::a::global:path.
|
||
//~^ ERROR: you should put `is::a::global:path` between ticks
|
||
/// be_sure_we_got_to_the_end_of_it
|
||
//~^ ERROR: you should put `be_sure_we_got_to_the_end_of_it` between ticks
|
||
fn foo_bar() {
|
||
}
|
||
|
||
/// That one tests multiline ticks.
|
||
/// ```rust
|
||
/// foo_bar FOO_BAR
|
||
/// _foo bar_
|
||
/// ```
|
||
/// be_sure_we_got_to_the_end_of_it
|
||
//~^ ERROR: you should put `be_sure_we_got_to_the_end_of_it` between ticks
|
||
fn multiline_ticks() {
|
||
}
|
||
|
||
/// This _is a test for
|
||
/// multiline
|
||
/// emphasis_.
|
||
/// be_sure_we_got_to_the_end_of_it
|
||
//~^ ERROR: you should put `be_sure_we_got_to_the_end_of_it` between ticks
|
||
fn test_emphasis() {
|
||
}
|
||
|
||
/// This tests units. See also #835.
|
||
/// kiB MiB GiB TiB PiB EiB
|
||
/// kib Mib Gib Tib Pib Eib
|
||
/// kB MB GB TB PB EB
|
||
/// kb Mb Gb Tb Pb Eb
|
||
/// 32kiB 32MiB 32GiB 32TiB 32PiB 32EiB
|
||
/// 32kib 32Mib 32Gib 32Tib 32Pib 32Eib
|
||
/// 32kB 32MB 32GB 32TB 32PB 32EB
|
||
/// 32kb 32Mb 32Gb 32Tb 32Pb 32Eb
|
||
/// be_sure_we_got_to_the_end_of_it
|
||
//~^ ERROR: you should put `be_sure_we_got_to_the_end_of_it` between ticks
|
||
fn test_units() {
|
||
}
|
||
|
||
/// This one checks we don’t try to split unicode codepoints
|
||
/// `ß`
|
||
/// `ℝ`
|
||
/// `💣`
|
||
/// `❤️`
|
||
/// ß_foo
|
||
//~^ ERROR: you should put `ß_foo` between ticks
|
||
/// ℝ_foo
|
||
//~^ ERROR: you should put `ℝ_foo` between ticks
|
||
/// 💣_foo
|
||
/// ❤️_foo
|
||
/// foo_ß
|
||
//~^ ERROR: you should put `foo_ß` between ticks
|
||
/// foo_ℝ
|
||
//~^ ERROR: you should put `foo_ℝ` between ticks
|
||
/// foo_💣
|
||
/// foo_❤️
|
||
/// [ßdummy textß][foo_1ß]
|
||
/// [ℝdummy textℝ][foo_2ℝ]
|
||
/// [💣dummy tex💣t][foo3_💣]
|
||
/// [❤️dummy text❤️][foo_4❤️]
|
||
/// [ßdummy textß](foo_5ß)
|
||
/// [ℝdummy textℝ](foo_6ℝ)
|
||
/// [💣dummy tex💣t](fo7o_💣)
|
||
/// [❤️dummy text❤️](foo_8❤️)
|
||
/// [foo1_ß]: dummy text
|
||
/// [foo2_ℝ]: dummy text
|
||
/// [foo3_💣]: dummy text
|
||
/// [foo4_❤️]: dummy text
|
||
/// be_sure_we_got_to_the_end_of_it
|
||
//~^ ERROR: you should put `be_sure_we_got_to_the_end_of_it` between ticks
|
||
fn test_unicode() {
|
||
}
|
||
|
||
/// This test has [a link_with_underscores][chunked-example] inside it. See #823.
|
||
//~^ ERROR: you should put `link_with_underscores` between ticks
|
||
/// See also [the issue tracker](https://github.com/Manishearth/rust-clippy/search?q=doc_markdown&type=Issues)
|
||
/// on GitHub (which is a camel-cased word, but is OK). And here is another [inline link][inline_link].
|
||
/// It can also be [inline_link2].
|
||
//~^ ERROR: you should put `inline_link2` between ticks
|
||
///
|
||
/// [chunked-example]: https://en.wikipedia.org/wiki/Chunked_transfer_encoding#Example
|
||
/// [inline_link]: https://foobar
|
||
/// [inline_link2]: https://foobar
|
||
|
||
/// The `main` function is the entry point of the program. Here it only calls the `foo_bar` and
|
||
/// `multiline_ticks` functions.
|
||
///
|
||
/// expression of the type `_ <bit_op> m <cmp_op> c` (where `<bit_op>`
|
||
/// is one of {`&`, '|'} and `<cmp_op>` is one of {`!=`, `>=`, `>` ,
|
||
/// be_sure_we_got_to_the_end_of_it
|
||
//~^ ERROR: you should put `be_sure_we_got_to_the_end_of_it` between ticks
|
||
fn main() {
|
||
foo_bar();
|
||
multiline_ticks();
|
||
test_emphasis();
|
||
test_units();
|
||
}
|
||
|
||
/// ## CamelCaseThing
|
||
/// Talks about `CamelCaseThing`. Titles should be ignored, see issue #897.
|
||
///
|
||
/// # CamelCaseThing
|
||
///
|
||
/// Not a title #897 CamelCaseThing
|
||
//~^ ERROR: you should put `CamelCaseThing` between ticks
|
||
/// be_sure_we_got_to_the_end_of_it
|
||
//~^ ERROR: you should put `be_sure_we_got_to_the_end_of_it` between ticks
|
||
fn issue897() {
|
||
}
|
||
|
||
/// I am confused by brackets? (`x_y`)
|
||
/// I am confused by brackets? (foo `x_y`)
|
||
/// I am confused by brackets? (`x_y` foo)
|
||
/// be_sure_we_got_to_the_end_of_it
|
||
//~^ ERROR: you should put `be_sure_we_got_to_the_end_of_it` between ticks
|
||
fn issue900() {
|
||
}
|
||
|
||
/// Diesel queries also have a similar problem to [Iterator][iterator], where
|
||
/// /// More talking
|
||
/// returning them from a function requires exposing the implementation of that
|
||
/// function. The [`helper_types`][helper_types] module exists to help with this,
|
||
/// but you might want to hide the return type or have it conditionally change.
|
||
/// Boxing can achieve both.
|
||
///
|
||
/// [iterator]: https://doc.rust-lang.org/stable/std/iter/trait.Iterator.html
|
||
/// [helper_types]: ../helper_types/index.html
|
||
/// be_sure_we_got_to_the_end_of_it
|
||
//~^ ERROR: you should put `be_sure_we_got_to_the_end_of_it` between ticks
|
||
fn issue883() {
|
||
}
|
||
|
||
/// `foo_bar
|
||
/// baz_quz`
|
||
/// [foo
|
||
/// bar](https://doc.rust-lang.org/stable/std/iter/trait.IteratorFooBar.html)
|
||
fn multiline() {
|
||
}
|