In reply to cgales:
Yes, I know that UVM components should not be cloned/copied/compared/recorded/etc.
However, the uvm_component has a Configuration Interface, which has the function: apply_config_settings :
https://verificationacademy.com/verification-methodology-reference/uvm/docs_1.2/html/files/base/uvm_component-svh.html#uvm_component.apply_config_settings
Trying to figure out what is its purpose?
In the description of the function there are some mentions of: `uvm_*_field macros
This what I was trying to point out.
What use cases could require usage of field macros for uvm_component?
I guess we cannot deny its usage for components as we do advise not to use it for uvm objects. Since we are not constructing/deconstructing uvm components many times during run-time.
So there is not much performance penalty…