Strange compile error related to length of string sent to sol::table.get<T> about sol2

[mattwigway]

I think this may be caused by a GCC bug. It looks like the GCC static analyzer is seeing that somewhere the function gets called with a null-terminated string of a certain length (30 in my case, I guess 10 with the null terminator in yours), and reads the whole thing, and assumes it will always read that many bytes. @FranchescaMullin is there somewhere else in your program where you have a nine-character argument to .get?

[FranchescaMullin]

You are definitely on to something!

My first call to get is the following (10 characters long):
sol::optional<std::string> pricerType = config.get<sol::optional<std::string>>("pricerType");

As an experiment to test your theory, I tried to compile it with the field name lengthened to 17 chars:
sol::optional<std::string> pricerType = config.get<sol::optional<std::string>>("pricerTypezzzzzzz");
and I get the following error:
/redacted/include/sol/stack_field.hpp:116:61: error: array subscript ‘const char [18][0]’ is partly outside array bounds of ‘const char [17]’ [-Werror=array-bounds] 116 | lua_getfield(L, tableindex, &key[0]);
The line of code generating the error is as follows (16 chars long):
config.get<sol::optional<std::string>>("frontMonthSymbol");

If I drop the number of chars in the first call to get to 16 chars, the whole thing compiles fine.