Berke

After this PR merged, i will open another PR for SIMD/NASM support for libjpeg-turbo.

I did include assembly files in this pull request. Should I remove them and include it with SIMD/NASM support for libjpeg-turbo? I rather to keep in this pull request because...

Next PR is ready. When this PR merged, i will rebase it and open it immediately.

I have limited time left in order to successfully complete GSoC and I am little behind. Lets merge SIMD pr if appropiate, after GSoC, if noone does, i will update...

@alalek I am planning to do Python and Java bindings after we finalize this API interface. Thanks for the reminder!

I think I can remove the cv::Exception part from the API and provide error codes. This way, API would be more efficient.

I made the fixes. Please take a look again @vpisarev @asmorkalov. ALso, the Windows10-x64 fail is not related with my pull request. Please rerun that workflow only if you can....

`at() calls operator[], but not vise versa. In case if index is -1 you'll get out of bound access for std::vector. For index, let say 1e+6 the next loop will...

The current iterator api does not implements operator->. Should I? ```cpp struct CV_EXPORTS iterator { Mat* operator->(); ... } Mat* ImageCollection::iterator::operator->() { CV_Assert(m_pCollection); return &m_pCollection->getImpl()->operator[](m_curr); } ``` So one can...

Further explanation about `operator++()` advance call. There are 2 variables named `m_curr` and `m_current`. Maybe I should rename them. * m_curr -> Iterator API * m_current -> ImageCollection API When...