Thanks for the reply. My comment apparently came off as trite, apologies. One of the enlightening things for me about CSP and Erlang, in particular, was using

Thanks for the reply. My comment apparently came off as trite, apologies. One of the enlightening things for me about CSP and Erlang, in particular, was using channels and messages and a bunch of lightweight tasks for flow control and state management. Reading the reddit comments, and even your reply here, seems to indicate that that type of programming isn't a good fit for rust, and that perfectly reasonable trade offs were made that led the language in a different direction. I should have phrased the comment better, but the recommendations here and in the reddit thread boil down to replying to "it hurts when I do this" with "don't do that". Obviously no-one is trying to write programs that count to 10001, but the capability of doing it that way efficiently opens up a bunch of different options. It will be interesting to see what happens to go's performance on things like this if they move away from segmented stacks.