3 ms·

This is different. They are combining streams in the original article. (‘Start with the stream of integers from 1 to infinity <…>’). Your code is take 10 mu

by lelf 13y ago

This is different. They are combining streams in the original article. (‘Start with the stream of integers from 1 to infinity <…>’). Your code is take 10 mutable_spaghetti_function

dkhenry 13y ago
And as a trade off you get a much cleaner and more performant solution to the same contrived problem. This is where Haskell and functional coders tend to break down. Yes its mutable, but by violating that one rule you gain so much in terms of readability and performance.
- 5hoom 13y ago
  That's one thing I've noticed with my C++ code lately is that I'm writing const absolutely everywhere. Having mutability where you need it is awesome but it is interesting to see languages like Rust where immutability is the default.
  - jzwinck 13y ago
    I have done a bit of this too. The main downside in C++ is that you end up writing a few more ternary operators than you otherwise may have. But it is nice to be able to look at the first assignment of a variable and know it is the only one.
    - 5hoom 13y ago
      Yeah it kind of feels dirty having all these mutable variables around after doing any functional programming at all. I've found using const a lot also goes hand-in-hand with raii. If a member of a class is const it must be initialized in the constructor, and it just seems to make me code a bit more "hygienically".
- cgh 13y ago
  You are right about more performant, but how is it cleaner and more readable than this? pyth x = [(a,b,c) | a<-[1..x], b<-[1..x], c<-[1..x], (a^2)+(b^2) == (c^2)]
  - dkhenry 13y ago
    Thats not c++ code. My claim is that if you try to stay pure using C++ you end up with very very ugly code that preforms pretty poorly.
jzwinck 13y ago
Indeed. This is part of why I included "idiomatic" in the title here. Someone smarter than me already wrote a bit prettier iterator increment function, and using that is easy once you have the interface decided. And in C++, iterators abound, and can be used as infinite sequence generators with no difference to how they are normally used and understood. The code may be spaghetti, but I mostly just lifted it from the referenced article and solved the problems the original author brought up, namely the separation of concerns. The C++ solution to this problem will never be as beautiful as the Haskell one, but I wanted to show it doesn't have to be alienating for people who program C++ daily. C++ iterators are powerful, and can be used for a lot more than stepping through a container. We write too few of them.

by lelf 13y ago

This is different. They are combining streams in the original article. (‘Start with the stream of integers from 1 to infinity <…>’). Your code is take 10 mutable_spaghetti_function

dkhenry 13y ago

And as a trade off you get a much cleaner and more performant solution to the same contrived problem. This is where Haskell and functional coders tend to break down. Yes its mutable, but by violating that one rule you gain so much in terms of readability and performance.

5hoom 13y ago
That's one thing I've noticed with my C++ code lately is that I'm writing const absolutely everywhere. Having mutability where you need it is awesome but it is interesting to see languages like Rust where immutability is the default.
- jzwinck 13y ago
  I have done a bit of this too. The main downside in C++ is that you end up writing a few more ternary operators than you otherwise may have. But it is nice to be able to look at the first assignment of a variable and know it is the only one.
  - 5hoom 13y ago
    Yeah it kind of feels dirty having all these mutable variables around after doing any functional programming at all. I've found using const a lot also goes hand-in-hand with raii. If a member of a class is const it must be initialized in the constructor, and it just seems to make me code a bit more "hygienically".
cgh 13y ago
You are right about more performant, but how is it cleaner and more readable than this? pyth x = [(a,b,c) | a<-[1..x], b<-[1..x], c<-[1..x], (a^2)+(b^2) == (c^2)]
- dkhenry 13y ago
  Thats not c++ code. My claim is that if you try to stay pure using C++ you end up with very very ugly code that preforms pretty poorly.

jzwinck 13y ago

Indeed. This is part of why I included "idiomatic" in the title here. Someone smarter than me already wrote a bit prettier iterator increment function, and using that is easy once you have the interface decided. And in C++, iterators abound, and can be used as infinite sequence generators with no difference to how they are normally used and understood. The code may be spaghetti, but I mostly just lifted it from the referenced article and solved the problems the original author brought up, namely the separation of concerns. The C++ solution to this problem will never be as beautiful as the Haskell one, but I wanted to show it doesn't have to be alienating for people who program C++ daily. C++ iterators are powerful, and can be used for a lot more than stepping through a container. We write too few of them.