]> git.lizzy.rs Git - rust.git/commit
Rollup merge of #49353 - chisophugis:patch-1, r=Mark-Simulacrum
authorTim Neumann <mail@timnn.me>
Mon, 26 Mar 2018 13:15:01 +0000 (15:15 +0200)
committerGitHub <noreply@github.com>
Mon, 26 Mar 2018 13:15:01 +0000 (15:15 +0200)
commit1233aa29de2d6f5e293f84b38ba2b02cfaf1fa0e
tree86e9a6450971d12a82eb18ead0b5036d6ffda0a8
parentd601e74675b5e92b2050c1f4454138a69e620f54
parentf198b0acf512458bdbe5079d12414ff94b03f7ac
Rollup merge of #49353 - chisophugis:patch-1, r=Mark-Simulacrum

Fix confusing doc for `scan`

The comment "the value passed on to the next iteration" confused me since it sounded more like what Haskell's [scanl](http://hackage.haskell.org/package/base-4.11.0.0/docs/Prelude.html#v:scanl) does where the closure's return value serves as both the "yielded value" *and* the new value of the "state".

I tried changing the example to make it clear that the closure's return value is decoupled from the state argument.