beached

Have you considered not doing this and then they put their value_to into a header that includes their type and the boost.json header. That accomplishes the same thing of firewalling...

It think this is the type you need is boost::string_view in non-freestanding mode

I think something that would help is using /api/v1/profile/current.json on nightscout to get the current settings as a default with the option to specify another. It would reduce a lot...

It isn't just Urchin on the pebble classic at least. All the CGM watch faces seem to have BT connectivity issues on the latest Pebble OS. I downgraded a few...

There are two major places that use it, one is always inlined and does a if constexpr over the tag to dispatch to the others. It could probably be switched...

I think this has been fixed. Or the sub functions are not using tag invoke where the genericness and open set to call isn't needed any longer.

I think MS Win ABI requires it for all user type https://learn.microsoft.com/en-us/cpp/build/x64-calling-convention?view=msvc-170 . It says all 1, 2, 4, 8 byte sized classes can be passed in a register, otherwise...

I have removed all the usages of tag types. If I missed any, I'll remove them. the debugging usage is no longer useful as my tooling is better and this...

At this point the abstractions are too coupled to JSON to be effective at msgpack. However one thing to keep in mind is that strings are going to be about...

Thanks for pointing this out. The issue is that it is throwing std::out_of_range there and the catch is looking for a json_exception with a NumberOutOfRange reason. I'll have to move...