Skip to content

bump(mcpp.plugins): 0.7.1, nothing in the package instantiates std::filesystem::path's iterator - #403

Merged
Sunrisepeak merged 1 commit into
mainfrom
bump/mcpp-plugins-0.7.1
Sep 12, 2026
Merged

bump(mcpp.plugins): 0.7.1, nothing in the package instantiates std::filesystem::path's iterator#403
Sunrisepeak merged 1 commit into
mainfrom
bump/mcpp-plugins-0.7.1

Conversation

@Sunrisepeak

Copy link
Copy Markdown
Member

Tracks mcpp-community/mcpp-plugins#18, tag v0.7.1. Under MSVC 14.52 (36629 and 36725, xrgui CI) a module whose BMI carries the path iterator poisons every importer that touches path again (C2801 at filesystem(1572)); 0.7.1 removes every instantiation from the package. GLOBAL archive hashed twice: a8d1b4dc8187c2b67a17d997245a4e4a3d52e26251f4c824fc5b951b58bbe293; CN asset published with gtc and read back byte-identical; latest 0.7.0 -> 0.7.1; local lints pass. Consumer: Sunrisepeak/xrgui#8.

…ilesystem::path's iterator

Under MSVC 14.52 (36629 and 36725, measured on xrgui's CI) a module whose
BMI carries std::filesystem::path's iterator poisons every importer that
touches path again:

    filesystem(1572): error C2801: '_Path_iterator<...>::operator ==' must be
    a non-static member

the STL's own hidden friend. 0.7.1 changes no member's interface: the lib
root reads paths apart as strings and the members' relative-path arithmetic
is one string helper. 0.7.0 is unusable on that toolset for any consumer
whose host modules touch a path, which is why `latest` moves.

Archive downloaded twice and hashed the same; CN asset published from that
file with gtc and read back byte-identical. No package in this index pins
mcpp.plugins.

mcpp-community/mcpp-plugins#18
@Sunrisepeak
Sunrisepeak merged commit 940ba7b into main Sep 12, 2026
8 checks passed
@Sunrisepeak
Sunrisepeak deleted the bump/mcpp-plugins-0.7.1 branch September 12, 2026 11:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant