个人理解:
for in 开销过多,而紧随着的block很快,导致误以为优化失败。其实优化成功,但是此处block太快,for in循环反而太多,导致效果不明显。
这里减少了for in 次数,延长block 执行时间,就可以明显观察到未被阻塞。但是如果要优化,还是需要加开for in 的情况下,才会效果明显吧。
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
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.
demo7 中,使用了实战优化,但是实际仍然卡在了App启动界面。
个人理解:
for in 开销过多,而紧随着的block很快,导致误以为优化失败。其实优化成功,但是此处block太快,for in循环反而太多,导致效果不明显。
这里减少了for in 次数,延长block 执行时间,就可以明显观察到未被阻塞。但是如果要优化,还是需要加开for in 的情况下,才会效果明显吧。