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
Is it possible to leverage version compatibility requirements in Requires.jl statements? I am bumping into issues like:
@require JuMP "..."...
where the optional dependency gets updated with breaking changes, and I can't control the version. Maybe adding an extra optional argument to the macro to be passed to the pkg manager?
@require JuMP x.y.z "..."...
The text was updated successfully, but these errors were encountered:
Is it possible to leverage version compatibility requirements in Requires.jl statements? I am bumping into issues like:
where the optional dependency gets updated with breaking changes, and I can't control the version. Maybe adding an extra optional argument to the macro to be passed to the pkg manager?
The text was updated successfully, but these errors were encountered: