scipy.special.binom和scipy.misc.comb有什么区别？(What's the difference between scipy.special.binom and scipy.misc.comb?)

 流迭代器为iostream的格式化提取/插入操作提供迭代器接口。 例如，请考虑以下几点： 
 
std::vector<int> v;

for (int n; std::cin >> n; )
    v.push_back(n);
 
 这相当于： 
 
std::vector<int> v(std::istream_iterator<int>(std::cin), 
                   std::istream_iterator<int>{});
 
 推进迭代器执行一次提取，类似于std::cin >> n ; 如果提取失败，则迭代器将采用奇异状态，这也是缺省构造的迭代器的状态。 
 
 就其性质而言，这些流迭代器是单遍的 ，即最弱的迭代器：您只能访问一次“范围”中的每个元素，并且永远不会返回; 并且从同一个流构建的两个非结束迭代器相等，尽管对于取消引用的值没有任何意义。 （但是请注意，如果你没有对迭代器进行解引用，那么是否曾经尝试过第一次提取是一种奇怪的缺乏特异性。） 
 
 为了完整性，可以类似地使用输出流迭代器来将流转换为“容器”，这对于使用迭代器的算法很有用： 
 
std::copy(v.begin(), v.end(), std::ostream_iterator<int>(std::cout, "\n"));
 
 输出流迭代器在分配给它时执行其工作; 其他操作是空操作。 
 
 
 有趣的是，没有一个包含getline的流迭代器; 人们经常自己写一个，因为迭代器接口在很多方面都很有用。 

Stream iterators provide an iterator interface to the formatted extraction/insertion operations of iostreams. For example, consider the following:
 
std::vector<int> v;

for (int n; std::cin >> n; )
    v.push_back(n);
 
This is equivalent to:
 
std::vector<int> v(std::istream_iterator<int>(std::cin), 
                   std::istream_iterator<int>{});
 
Advancing the iterator performs one exraction, akin to std::cin >> n; if the extraction fails, the iterator assumes the singular state, which is also the state of the default-constructed iterator.
 
By their very nature, these stream iterators are single-pass, i.e. the weakest kind of iterator: You can only visit each element in the "range" once, and never go back; and two non-end iterators built from the same stream compare equal although that does not have any meaning regarding the dereferenced value. (But note that there's a curious lack of specificity as to whether the first extraction is ever attempted if you don't dereference the iterator ever.)
 
Just for completeness, output stream iterators can be used similarly to turn a stream into a "container", useful for algorithms that work with iterators:
 
std::copy(v.begin(), v.end(), std::ostream_iterator<int>(std::cout, "\n"));
 
Ouput stream iterators perform their work when assigned to; the other operations are no-ops.
 
 
Interestingly enough, there isn't a stream iterator that wraps getline; people often write one themselves, because iterator interfaces are useful in many ways.