# Inconsistent behavior of \`sum\`,\`mean\` (and probably others) on different collection types

**URL:** https://discourse.julialang.org/t/inconsistent-behavior-of-sum-mean-and-probably-others-on-different-collection-types/1167
**Category:** Internals & Design
**Created:** [December 27, 2016, 7:11pm UTC](https://discourse.julialang.org/t/inconsistent-behavior-of-sum-mean-and-probably-others-on-different-collection-types/1167 "2016-12-27T19:11:45Z")
**Posts on this page:** 1
**Showing post:** 9

<div class="post-metadata">

### Author: ![stevengj](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/stevengj/32/71_2.png) [@stevengj](https://discourse.julialang.org/u/stevengj)
#### Post date: [December 28, 2016, 2:58am UTC](https://discourse.julialang.org/t/inconsistent-behavior-of-sum-mean-and-probably-others-on-different-collection-types/1167/9 "2016-12-28T02:58:36Z")

</div>

> [@ScottPJones](#):
>
> You are still focusing on the issues of promotion. What about the issue of inconsistent results from different container types (even when the iterators produce the exact same values in the same order)?

The question of `Tuple` handling is separate; I tend to agree with @nalimilan that `sum` should probably treat arrays and tuples similarly with respect to promotion.

A tip that you’ve heard before: raising multiple independent issues in a single thread confuses the discussion. Nor does calling design decisions you disagree with (or the absence of features you would like) “bugs” or “broken” facilitate productive discourse.

---

_[View the full topic](https://discourse.julialang.org/t/inconsistent-behavior-of-sum-mean-and-probably-others-on-different-collection-types/1167)._