优化了对象池返回对象的代码#2
Merged
Merged
Conversation
Author
|
如果觉得有不合理的地方恳请指出。 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
我优化了对象池模式的部分代码。原版本中，返回对象实例到对象栈需要从传入的GameObject中GetComponent到PoolObject。在绝大多数应用场景，对象池返回对象（ReturnObjectToPool）是一个很频繁的行为，频繁调用GetComponent会造成CPU的开销。解决方案是将案例代码中的列表类型从GameObject改
为PoolObject并修改涉及到的逻辑。
已经测试效果与原来的一致。
工程版本升级到2018.1版本，可以相互兼容。
Can't you add it?