![]() ![]() ▪ Made the red underline smarter about errors at the EOL. ▪ Added a tooltip the IntelliBox that show info about the selected item (name, return type, member type). (toe_head2001) ▪ Added toggles for the LineNumber margin and the CodeFolding margin (see View menu). (toe_head2001) ▪ Replaced the icons in the IntelliBox with ones that are more akin to the icons in recent versions of VS. (toe_head2001) ▪ Alignment fixes for the IntelliBox when the document is at different zoom levels. (toe_head2001) That assumes that the setup is done so that no global variable is set to a value, then changed. The worst that will happen is some extra threads will do the setup. It wouldn't be the first time for things like this.ĪDDED: Because the dirty flag isn't cleared until the setup is complete, the method doesn't depend on a single thread running first (even though that's how it works). I don't see why this idea is especially risky, but I certainly could be overlooking something. This changes a bunch of comparisons to a singe one. You can, and I've done that in a few CodeLab plugins where the cost of doing the setup is quite high (like generating a table), but it's a rather ugly, messy way to do it, in my opinion and while caching and comparisons may be cheaper than the setup, they aren't free when there are a lot of values (I realize the branches will be correctly predicted most of the time). Also, can't you do this yourself? Cache the old value of the token, and compare the values of old vs. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |