git.lizzy.rs Git - rust.git/commit - src/librustc

]> git.lizzy.rs Git - rust.git/commit - src/librustc_llvm/build.rs

author	bors <bors@rust-lang.org>
	Mon, 20 Jul 2020 10:19:58 +0000 (10:19 +0000)
committer	bors <bors@rust-lang.org>
	Mon, 20 Jul 2020 10:19:58 +0000 (10:19 +0000)
commit	71384101ea3b030b80f7def80a37f67e148518b0
tree	b2cdb190bf396f3b8fc7ffb65e6b0145d27bfd9d	tree \| snapshot
parent	05630b06fdf76c25c6ccf2e9ac3567592eae6c67	commit \| diff
parent	76b8420168a2e14abf025a07ee4e32d87956d940	commit \| diff

Auto merge of #74010 - pierwill:pierwill-o-notation, r=GuillaumeGomez

Use italics for O notation

In documentation, I think it makes sense to italicize O notation (*O(n)*) as opposed to using back-ticks (`O(n)`). Visually, back-ticks focus the reader on the literal characters being used, making them ideal for representing code. Using italics, as far I can tell, more closely follows typographic conventions in mathematics and computer science.

Just a suggestion, of course! 😇

Empowering everyone to build reliable and efficient software.

RSS Atom

src/liballoc/collections/vec_deque.rs	diff1 \|	diff2 \|	blob \| history
src/liballoc/string.rs	diff1 \|	diff2 \|	blob \| history
src/libcore/slice/mod.rs	diff1 \|	diff2 \|	blob \| history
src/librustc_index/bit_set.rs	diff1 \|	diff2 \|	blob \| history