I\'m getting this warning on a stack variable:
warning: object.member may be used uninitialized in this function
In this case I do not wish to
@Nawaz has answered the question as specifically asked, but have you considered that the fact that you need this may indicate you're declaring your struct
too early/at a less nested scope than appropriate? It would generally be much preferred if you could declare your struct
at a point where you can actually initialize it rather than declaring it earlier and filling it in various locations.
Also, even though you can verify that it's never used uninitialized right now, what if someone else adds a new code path in the future and it's not initialized properly? If you disable the warning then it'll silently compile and probably break in an unexpected way. Unless you can prove that the initialization is taking a measurable amount of your program's CPU it's probably better to just do the initialization up front.