v0.2.0

[EmJayGee]

Rework the string conversion framework so that everything is dispatched through the m::string_converter<fromtype, totype> type.

This was a lot of work but it also got rid of a lot of "organic growth" that had occurred.

Also made the executive decision that nullptr null terminated strings would map to the empty string, not a no-value optional string. The work to try to handle / preserve m::not_null<char_type const*> throughout, and then to deal with the ramifications of a relatively simple desire, like m::to_string(some_function_that_returns_wstring().c_str()) was kind of insane.

Updated to 0.2.0 only so that now we will burn through the "minor" version number as "feature" releases are made and the "patch" releases when I'm trying to iron out kinks in the vcpkg or CMake installation that had gotten messed up.

I had started this with 0.1.0, but then I was having (unrelated) problems with it, and tried making a 0.1.1, and also had problems so deleted those releases and reverted to 0.0.x for a bit but I'm pretty sure that the problems I was having were only due to the tool set I was using elsewhere being old so it's all cleared up now.

If someone happens to be reading this and has good GitHub action coding skills, I'd like to implement something in our CI so that during PR validation, the CI kicks off a vcpkg install of a port referring to the same git commit. To do this I think we need to write a custom action to write the portfile.cmake with the commit id and hash or something like that; perhaps the vcpkg.json in the testing port needs to be written to also?

What's Changed

• Rework the string conversion and transcoding infrastructure by @EmJayGee in Rework the string conversion and transcoding infrastructure #128

Full Changelog: v0.0.65...v0.2.0

---

This discussion was created from the release v0.2.0.