Mateusz Łoskot

> FYI, I reported the issue here, https://developercommunity.visualstudio.com/t/INTERNAL-COMPILER-ERROR-compiling-std::v/10011526 [Latest update](https://developercommunity.visualstudio.com/t/INTERNAL-COMPILER-ERROR-compiling-std::v/10011526#T-N10024311): _"A fix for this issue has been internally implemented and is being prepared for release. "_

@Sayan-Chaudhuri >how to do so what you have mentioned? Please, read the CONTRIBUTING.md on updating your PR. Updating/Syncing PR on GitHub is a common operation, so it is very well...

I may vaguely recall that I agreed with @miralshah365 to begin with support unsigned integer channel types only. There should be at least a static assertion though as a documentation...

First, I'm a huge supporter of incorporating clang-format. I'm happy to be not a lonely one :) Have you seen these? - https://github.com/boostorg/gil/pull/87 - [example/clang-format](https://github.com/boostorg/gil/blob/23702f9879e81bb3b08971eb153b199ea56bb0af/example/clang-format/)

I personally give - higher priority to **consistent** coding style and formatting throughout the whole codebase - lower priority to what particular coding style is used As long as the...

I'd add to the overall discussion this RFC of mine https://trac.osgeo.org/geos/wiki/RFC4 where some details and implications are discussed, including external references, especially three parts of MongoDB story how they managed...

We should give this a try :-) https://www.youtube.com/watch?v=_EaU3VsDOJM > Clang Format Detector automatically finds the best matching Clang-Format Style for your code files.

Once we agree on the definition of [.clang-format](https://github.com/boostorg/gil/tree/23702f9879e81bb3b08971eb153b199ea56bb0af/example/clang-format), I don't mind either exploring the history rewrite option or just swallowing the "big reformat" pill.

@sdebionne > Is there any Boost wide .clang-format that we could use? No, or I don't know about any, but some individual libraries have some (including us): ``` /d/boost.win (develop...

You're welcome to give it a go, but be warned its not a quick bit of work. Instead of diving deep, you can help @lpranam with collecting the image processing...