Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tracking issue: Packages/extensions #31

Open
daemontus opened this issue Dec 7, 2024 · 1 comment
Open

Tracking issue: Packages/extensions #31

daemontus opened this issue Dec 7, 2024 · 1 comment

Comments

@daemontus
Copy link
Member

I'll try to keep ideas/discussion about packages in this thread.

@daemontus
Copy link
Member Author

SBase

Currently, SBase implicitly assumes that everything will use the core SBML namespace. For packages, this isn't really going to work. One possible way to fix this is to declare a Namespace trait (or Package?), and then make SBase generic with types implementing this trait. That way, we can say that Model implements SBase<Core> while QualModel implements SBase<Qual> and so on. Of course, in this scenario, QualModel can be still cast to Model. We'll need to think about how this affects the attributes (which can either use the package namespace, or the default namespace, either is fine).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant