Warns about parameters passed by value being assigned a new value in the body of a procedure.
New This feature is currently only available in pre-release builds (or the xmldoc asset doesn’t yet exist on
Inspection type: CodeQualityIssues
Debugging is easier if the procedure's initial state is preserved and accessible anywhere within its scope. Mutating the inputs destroys the initial state, and makes the intent ambiguous: if the calling code is meant to be able to access the modified values, then the parameter should be passed ByRef; the ByVal modifier might be a bug
The following quick-fixes are available for this inspection:
Each example is a self-contained MCVE showing the feature in a single specific scenario.
Module1by default, these are general-purpose standard procedural modules.
Class1by default, these modules define the default interface for an object of that type.
VB_PredeclaredIdattribute set to
True(with or without a
@Interfaceannotation) whose default interface is not a class type intended to be instantiated.
The following code should trigger this inspection:
The content of this page was generated from xml/comments in the source code compiled into
Edit this page