Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Documentation for ReturnsNextFromSequence is incorrect #273

Closed
Dashue opened this issue Mar 7, 2014 · 7 comments · Fixed by #290
Closed

Documentation for ReturnsNextFromSequence is incorrect #273

Dashue opened this issue Mar 7, 2014 · 7 comments · Fixed by #290

Comments

@Dashue
Copy link
Contributor

Dashue commented Mar 7, 2014

"Null will be returned when all the values in the sequence has been returned."
It actually seems to return default, 0 for a sequence of integers

@Dashue
Copy link
Contributor Author

Dashue commented Mar 7, 2014

I'll fix this once my Task overloads of Returns, ReturnsLazily and ReturnsNextFromSequence is done

@blairconrad
Copy link
Member

Setting to P3 and Ready and taken by @Dashue. Thanks, @Dashue!

@blairconrad blairconrad added this to the 1.19 milestone Mar 7, 2014
@adamralph
Copy link
Contributor

+1 some poor grammar in there too! 😉

@blairconrad
Copy link
Member

I'm looking forward to this fix, but be aware that the actual behaviour is a little more complicated than "return default<T>. It's "revert to doing whatever you would've been doing had we not called ReturnsNextFromSequence". @Dashue, I expect that you tested by taking an otherwise-unconfigured method, so after the sequence was finished, the behaviour reverted to default unconfigured behaviour, which is (often) return default.

Perhaps the best fix is to just not make promises about what happens after the sequence is exhausted. As far as I know, we don't make promises about what happens once we're done with a Once or Twice call…

@adamralph adamralph removed this from the 1.19 milestone Mar 20, 2014
@adamralph
Copy link
Contributor

Removing 1.19 milestone since we have other stuff ready to go live.

@adamralph
Copy link
Contributor

assigned 1.19 milestone

@blairconrad blairconrad modified the milestone: 1.19 Apr 14, 2014
@blairconrad
Copy link
Member

@Dashue, thanks very much for raising this issue. Look out for your name in the release notes 🏆

https://www.nuget.org/packages/FakeItEasy/1.19.0
https://github.com/FakeItEasy/FakeItEasy/releases/tag/1.19.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants