JavaScript is not currently enabled, but is required for full CodeSonar manual search and browse functionality.
If you are viewing this file in your hub's Web GUI, enable JavaScript in your browser: you will also need it for GUI functionality.
If you opened this file directly from disk, your browser may be directly suppressing JavaScript functionality: certain browsers perform this suppression on local files (but not files delivered by web servers) for security reasons.
| CodeSonar® 28.0w | AdaCore Inc |
Instantiating a generic lambda requires an implicit variable capture that was not established during the initial template-dependent scan of its body.
| Class Name | Cannot Capture Variable |
|---|---|
| Significance | style |
| Mnemonic | PARSE.CANNOT.CV |
| Categories | None |
| Availability | Available for C and C++. |
| Enabling | Checks for this warning class are enabled by default.
However, warning instances of this class that are issued as parser
errors (rather than parser warnings)
will be discarded
when using factory configuration settings.
To prevent these instances from being discarded, add the
following WARNING_FILTER rule to the project configuration file.
WARNING_FILTER += allow class="Cannot Capture Variable" WARNING_FILTER += discard class="Cannot Capture Variable" |
struct PlainSample { };
void inspect(int reading)
{
auto sample = [=](auto tag) {
using Tag = decltype(tag);
__if_exists(Tag::marker) {
int reading = 0;
}
return reading; // 'Cannot Capture Variable' warning issued here
};
(void)sample(PlainSample{});
}
To reproduce this example, analyze it with the following configuration:
WARNING_FILTER += allow class="Cannot Capture Variable"
The Microsoft __if_exists extension conditionally includes declarations. During the initial template-dependent scan, the local reading declaration hides the function parameter. When the lambda is instantiated with PlainSample, that declaration is omitted because the type has no marker member. The return expression then refers to the function parameter, for which no capture was established. Explicitly capturing reading avoids this diagnostic.
The following configuration file parameters affect checks for this warning class.
To report problems with this documentation, please visit https://support.adacore.com/csm.