-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Params compatibility with initialisation variables #18
Comments
It is already in place. For instance:
The issue I suppose is finding when the param is set outside the function code, like this scenario:
This gets very complex to detect. I may put in place something to detect it, but the best way of making sure your code is robust is explicitly defining your variables inside the function. (e.g. |
if you really want your param be nil by default, you can also set nil explicitly to mute the IDE. |
by the way: and to make your functions even more robust, you should also whitelist types like this: |
There is now a check for nil values. |
do you mean youre showing those as warning now as well? :O |
but technically nil means undefined, so actually youre right. damnit |
Would it be possible to add variable initialisation recognition for parameters?
example:
_ZCP_RWB_data is marked as an UNinitialized variable
The text was updated successfully, but these errors were encountered: