Renato Garcia

@mloskot At 4325be7 (boost-1.72.0) both [my code](https://github.com/boostorg/gil/issues/223#issue-402850795) (manual image checking) and [@codejaeger one](https://github.com/boostorg/gil/issues/223#issuecomment-594664605) was working fine. At c887d3b (develop head) my test works fine, but the one of codejaeger test...

@mloskot Oh man, sure! You are right! The code at [here](https://github.com/boostorg/gil/issues/223#issuecomment-594664605) when calling `gray16_image_t expected(dim,gray16_pixel_t(1))`, before 5f3c002 was actually calling [this](https://github.com/boostorg/gil/blob/5f3c00244bdc8128d53fa569d17a12a8b80642db/include/boost/gil/image.hpp#L64) constructor. As no constructor with signature `image(const point_t&, const...

IMO, although there are another question, the bug reported on this issue was solved. Should I close it?

I was not aware of dbg-macro until now. Nice library, thank you point it out! I definitively will take some ideas and inspirations from it.

About the features differences, beyond the ones that you have cited I would put that Icecream has support for printing wide characters, can print structs without `iostream

Currently there are no support to inspect channels separately. But that is a cool idea, it would be nice to show only the first channel with a command like: `cv_imshow...

Good catch! Thanks! When you do `A = cv2.imread("path/to/hbl.png")` `A` will be a `(200, 200, 3)` image. when you do `I=cv2.imread("path/to/hbl.png")[:,:,0]` `I` will be a `view` of shape `(200, 200)`...

Do you have a minimal example code, where this problem happens? So I could reproduce it.

Cut the code to the absolute minimum that reproduces the problem. If even then it is too big to post here, you can use [Github Gis](https://gist.github.com/)t and post the link...

Are you sure that the `mat_name` variable is on scope at the line where you set your breakpoint? Could you share a minimal working example where this error appears?