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

Create safety feature for diverging MATLAB bindings and MATFrost package. #69

Open
jorisbelierasml opened this issue Sep 13, 2024 · 0 comments

Comments

@jorisbelierasml
Copy link
Collaborator

The MATLAB component (.m, .mex) should be generated from the used MATFrost version. Currently as the installation requires a manual step. MATFrost.install() it could mean that a MATFrost package gets updated without updating the associated MATLAB files.

  1. Ideally during instantiate/resolve/update of the environment, the MATLAB bindings are regenerated.
  2. If not possible, add potential guards that check if the MATLAB bindings are up-to-date with the MATFrost package.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant