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 Nov 15, 2023. It is now read-only.
Currently the PHY abstract class is restricting all the PHY models that would be implemented to have MapOfSignals.
This is not optimal, as all models will inherit such members. They should be free to use whatever structures they would find appropriate.
Proposal
Remove the members limiting the implementation of different PHY models
Links / references
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Description
Currently the PHY abstract class is restricting all the PHY models that would be implemented to have MapOfSignals.
This is not optimal, as all models will inherit such members. They should be free to use whatever structures they would find appropriate.
Proposal
Remove the members limiting the implementation of different PHY models
Links / references
The text was updated successfully, but these errors were encountered: