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
- MSAA warnings are thrown when custom post-processing is used and the Scene contains transparent GameObjects
- Texture looks point-sampled when Mipmap Streaming is enabled
- Assigned font's bold/font-weight styles render using Default Font's assets when Default Font has corresponding style assets defined in TMP Settings
- "Modifying the parent of a VisualElement while it’s already being modified is not allowed" error is thrown when entering text and pressing tab in the Search window
- Mesh colliders are not updating their positions of bounds correctly
skiplist
Mar 29, 2015 09:33
How come this is by design?