Polyspace: expression must have a constant value

7 views (last 30 days)
Hello guys,
I have this C++17 code:
#define I2C_BUS_MAX_BUS_ITEMS 3
struct my_bus_t {
int bus{-1};
bool is_external;
};
static inline constexpr my_bus_t initBus(int bus)
{
my_bus_t ret{};
ret.bus = bus;
ret.is_external = false;
return ret;
}
constexpr my_bus_t buses[I2C_BUS_MAX_BUS_ITEMS] = {
initBus(1),
initBus(2),
};
This is the configuration setting.
It compiles well, but there is a problem in Polyspace: "expression must have a constant value".
Thank you in advance.
  2 Comments
Zulham Mr
Zulham Mr on 28 Apr 2022
constexpr my_bus_t buses[I2C_BUS_MAX_BUS_ITEMS] = {
initBus(1),
initBus(2),
};
This one.

Sign in to comment.

Accepted Answer

Anirban
Anirban on 29 Apr 2022
Edited: Anirban on 29 Apr 2022
You are initializing a three-element constexpr array with only two elements. If you change the line:
constexpr my_bus_t buses[I2C_BUS_MAX_BUS_ITEMS] = {
initBus(1),
initBus(2),
};
To something like:
constexpr my_bus_t buses[I2C_BUS_MAX_BUS_ITEMS] = {
initBus(1),
initBus(2),
initBus(2)
};
The error will go away. I am not sure why your compiler did not flag this.
  3 Comments
Anirban
Anirban on 2 May 2022
The C++ reference for constexpr states that constexpr variables must be immediately initialized.
In this case, you have partially initialized the array. This is not an error by itself, and my guess is, that is why the compiler does not complain. If you try to initialize the uninitialized elements later, the compiler should show an error.
Indeed, Polyspace is being stricter than your compiler. But, as you can see, partially initializing a constexpr array is an error because it cannot be initialized fully later.

Sign in to comment.

More Answers (0)

Community Treasure Hunt

Find the treasures in MATLAB Central and discover how the community can help you!

Start Hunting!