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

add more examples to foldable.md #824

Merged
merged 2 commits into from
Jan 30, 2016
Merged

Conversation

stew
Copy link
Contributor

@stew stew commented Jan 23, 2016

No description provided.

@codecov-io
Copy link

Current coverage is 89.30%

Merging #824 into master will increase coverage by +0.18% as of 8cf484d

@@            master   #824   diff @@
=====================================
  Files          168    168       
  Stmts         2309   2319    +10
  Branches        75     75       
  Methods          0      0       
=====================================
+ Hit           2058   2071    +13
  Partial          0      0       
+ Missed         251    248     -3

Review entire Coverage Diff as of 8cf484d

Powered by Codecov. Updated on successful CI builds.

@adelbertc
Copy link
Contributor

👍

after looking at only one value:

```tut
Foldable[Stream].foldRight(allFalse, Eval.now(true))((a,b) => Eval.now(a && b.value)).value
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think that (a,b) => Eval.now(a && b.value) would need to be something like (a,b) => if (a) b else Eval.now(false) in order to be stack safe if there were say 10k true values prepending the continually false values. So it might be a good idea to avoid calling .value until the very end, since that's what you usually want to do with Eval to achieve stack safety.

Having said that, I just gave it a try and it looks like the Cats foldRight implementation for Stream isn't actually stack safe. I'll create a separate issue for that.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I really mean this as a toy example to demonstrate the laziness. I think that it is clearer to read as is. but if you say please I'll change it :)

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm yeah, I see your point. It just seems bad to me to write an implementation that isn't stack-safe when a few lines above calls out that the std lib foldRight would hit a stack overflow. And if this is where people come to learn about foldRight, I'd want them to see examples of how to do it "right". I don't want to be a stick in the mud here though, so maybe I should just let it go :)

@ceedubs
Copy link
Contributor

ceedubs commented Jan 30, 2016

I guess I should have just said "please" :)

Thanks, @stew! Good stuff.

ceedubs added a commit that referenced this pull request Jan 30, 2016
add more examples to foldable.md
@ceedubs ceedubs merged commit 3cbc882 into typelevel:master Jan 30, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants