Skip to content

Navigation Menu

Explore
By size
By industry
By use case
Topics
Explore
- GitHub Sponsors
  Fund open source developers
- The ReadME Project
  GitHub community articles
Repositories
- Enterprise platform
  AI-powered developer platform
Available add-ons
Pricing

Search code, repositories, users, issues, pull requests...

Search

Clear

Search syntax tips

Provide feedback

We read every piece of feedback, and take your input very seriously.

Include my email address so I can be contacted

Saved searches

Use saved searches to filter your results more quickly

Name

Query

To see all available qualifiers, see our documentation.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.

Dismiss alert

JetBrains / resharper-unity Public

Notifications You must be signed in to change notification settings
Fork 132
Star 1.2k

Code
Issues 279
Pull requests 3
Actions
Projects 1
Wiki
Security
Insights

Additional navigation options

Code
Issues
Pull requests
Actions
Projects
Wiki
Security
Insights

Accessing multidimensional arrays is inefficient

Jump to bottom

Matt Ellis edited this page Mar 26, 2020 · 1 revision

To be completed

Toggle table of contents Pages 32

Loading
Home
Loading
Accessing multidimensional arrays is inefficient
Loading
Asset serialization mode
Loading
Attribute is redundant when applied to this declaration type
Loading
Avoid multiple unnecessary property accesses
Loading
Avoid null comparisons against UnityEngine.Object subclasses
Loading
Avoid usage of AddComponent in performance critical code
Loading
Avoid usage of Debug.Log methods in performance critical context
Loading
Avoid usage of Find methods in performance critical context
Loading
Avoid usage of GetComponent methods in performance critical context
Loading
Avoid using allocating versions of Physics Raycast functions
Loading
Avoid using Object.Instantiate without “Transform Parent” parameter and using SetParent later
Loading
Avoid using string based Method Invocation
Loading
Avoid using string based names for setting and getting properties on Animators, Shaders and Materials
Loading
base.OnGUI() will print "no GUI implemented" in the Unity inspector
Loading
Camera.main is inefficient in frequently called methods
Loading
Enabling shader keywords
Loading
MonoBehaviors must be instantiated with GameObject.AddComponent instead of new
Loading
Order of multiplication operations is inefficient
Loading
Performance critical context and costly methods
Loading
Possible mis application of FormerlySerializedAs attribute to multiple fields
Loading
Possible unintended bypass of lifetime check of underlying Unity engine object
Loading
Prefer using generic method overload instead of string
Loading
Redundant FormerlySerializedAs attribute
Loading
Redundant HideInInspector attribute
Loading
Redundant InitializeOnLoad attribute
Loading
Redundant SerializeField attribute
Loading
Redundant Unity event function
Loading
ScriptableObjects must be instantiated with ScriptableObject.CreateInstance instead of new
Loading
Switching code analysis context for hlsl cginc files in Rider
Loading
Troubleshooting debugging Unity players
Loading
Use CompareTag instead of explicit string comparison

Clone this wiki locally

Footer

© 2024 GitHub, Inc.

Footer navigation

Terms
Privacy
Security
Status
Docs
Contact

You can’t perform that action at this time.