Aso is a cached object. After the class is compiled, it will generate an Aso file in its own cache. When you test this file again, the related class system will make a comparison, and no compilation is needed if there is no change.
That is to say, saving time for testing output in the future!
It means caching, but in fact, when you directly overwrite a class file, sometimes the old one is used for release. Use this to clear it at this time. I feel like this ...... Accelerate your compilation But sometimes you changeCodeIt still uses the cache, and you need to remember to clear it. If you modify the original file, then sometimes there will be an error, then you have to delete the Aso file to be normal As mentioned above, when you overwrite the original file or save an exception (such as shutdown )! Clear that Aso can solve some exceptions! I don't understand anything else! |