Search Issue Tracker
By Design
Votes
0
Found in
5.0.0f4
Issue ID
683862
Regression
No
Using or not using the 'new' keyword gives conflicting warnings in the Editor and when building to any platform
How to reproduce:
1. Open attached project
- Notice the warning upon compilation
2. Add a 'new' keyword after the 'private' keyword in the script
- The editor gives no warnings
3. Build to any platform
- Notice Unity gives a warning that 'new' is not necessary
For a simple workaround, please surround the offending code like this:
#pragma warning disable 0108
private Rigidbody rigidbody = null;
#pragma warning restore 0108
This disables (and then reenables) the Editor warning that says that 'rigidbody' is being hidden.
Comments (1)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture Import Warnings are obscured by other Terrain Layer options in the Inspector
- Active Targets section text in Graph Inspector is truncated despite available space
- Burst Inspector middle divider is jittering when resized with the Burst Inspector window docked
- Shader Graph Node information is briefly displayed in Graph Inspector when clicking on Category in the Blackboard
- JsonConvert conversion fails trying to call GetCallbackMethodsForType when [OnDeserialized] is used in a class
skiplist
Mar 29, 2015 09:33
How come this is by design?