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
Because the HDL doesn't change, the IDE never knows to invalidate the previously compiled version.
Simple option: IDE never caches schematic-defined files, by hardcoding the class name
More advanced option: a class in the Block hierarchy directs the IDE to not cache subclasses
The most general option: A class in the Block hierarchy defines a function that evaluates to a caching key - in this case, it can be the schematic last-modified-date or hash. Every compiler run, either all blocks have their caching key updated (which can be inefficient), or blocks can be invalidated-on-first-use (more complex).
The text was updated successfully, but these errors were encountered:
Because the HDL doesn't change, the IDE never knows to invalidate the previously compiled version.
Simple option: IDE never caches schematic-defined files, by hardcoding the class name
More advanced option: a class in the Block hierarchy directs the IDE to not cache subclasses
The most general option: A class in the Block hierarchy defines a function that evaluates to a caching key - in this case, it can be the schematic last-modified-date or hash. Every compiler run, either all blocks have their caching key updated (which can be inefficient), or blocks can be invalidated-on-first-use (more complex).
The text was updated successfully, but these errors were encountered: