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
{{ message }}
This repository has been archived by the owner on Aug 20, 2024. It is now read-only.
Description:
The LoadMemoryAnnotation uses a ComponentName annotation to
describe the Memory to be loaded. We should eliminate deprecations like this
What is the expected behavior?
The code is clean without these warnings. If we do not fix or fail to mark the
LoadMemoryAnnotation as also deprecated we limit our ability to follow
through on removing the deprecated code on the next API changing release
Strategy:
I think the answer here is that we need to deprecate LoadMemoryAnnotation and create a new parallel one that uses ReferenceTarget or other modern for of firrtl locator
The text was updated successfully, but these errors were encountered:
Type of issue: Code cleanup, release issue
Description:
The LoadMemoryAnnotation uses a ComponentName annotation to
describe the Memory to be loaded. We should eliminate deprecations like this
What is the expected behavior?
The code is clean without these warnings. If we do not fix or fail to mark the
LoadMemoryAnnotation as also deprecated we limit our ability to follow
through on removing the deprecated code on the next API changing release
Strategy:
I think the answer here is that we need to deprecate LoadMemoryAnnotation and create a new parallel one that uses ReferenceTarget or other modern for of firrtl locator
The text was updated successfully, but these errors were encountered: