Mateusz Łoskot

@renatoGarcia > The used system is an up to date ArchLinux with gcc 8.2.1, boost 1.69, libpng 1.6.36. Is it possible for you to try the current `develop` branch?

@renatoGarcia I'd argue the fix in 5f3c00244bdc8128d53fa569d17a12a8b80642db is correct and if it breaks anything, then that thing needs fixing.

TBH, I'm a bit lost about what is fixed what is not, what MWE is correct and what not, but I don't have time now to check myself, so let's...

@Sayan-Chaudhuri If you don't see any related PR or commits or code then the answer is No.

@Scramjet911 Please, add the PR `#NNNN` reference to the description of this issue, so it is clear what to follow.

You've marked it as WIP, means you are still working on it aka not ready for review.

See https://github.com/boostorg/gil/blob/develop/CONTRIBUTING.md#pull-requests The WIP is an equivalent of marking a PR as Draft: - https://github.blog/2019-02-14-introducing-draft-pull-requests/ - https://github.blog/changelog/2020-04-08-convert-pull-request-to-draft/ The issue with Draft is that > Any user with **write access** to...

I've updated this issue with C++17 `std::filesystem`: > It is reasonable to replace the boost::filesystem with std::filesystem whenever GIL code is compiled using C++17, unless user explicitly desires to use...

This is included in the planning towards C++14/17 discussion here https://github.com/boostorg/gil/discussions/676

I'm not sure how the OP imagined this suggestion in detail, but for `View& base()` we definitely need some extra info cached: ``` template class image_view { using base_type =...