Skip to content

Conversation

@amontoison
Copy link
Member

close #213

cc @frapac

@sshin23
Copy link

sshin23 commented Nov 13, 2024

I wonder if it would make more sense to implement something like ma27a, which multiple dispatches it to ma27as, ma27ad, ma27aq, etc

@amontoison
Copy link
Member Author

amontoison commented Nov 13, 2024

I already did this for GALAHAD:

The underlying idea is to use an additional first argument (the float type) for dispatch.
I could add an additional layer to do this dispatch, you're right.

@sshin23
Copy link

sshin23 commented Nov 13, 2024

I think it would be good to have that layer. Then, e.g., MadNLPHSL can just rely on ma27a and things will automatically work once QuadMath is imported

@amontoison
Copy link
Member Author

I think it would be good to have that layer. Then, e.g., MadNLPHSL can just rely on ma27a and things will automatically work once QuadMath is imported

Should I do a double layer with the integer type as well?
I opened the PR #216 with the new symbols.

@amontoison
Copy link
Member Author

I think it would be good to have that layer. Then, e.g., MadNLPHSL can just rely on ma27a and things will automatically work once QuadMath is imported

Done in #220
Example with ma27ar:
https://github.com/JuliaSmoothOptimizers/HSL.jl/blob/main/src/Fortran/hsl_subset/ma27.jl#L25-L74

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

Successfully merging this pull request may close these issues.

Interface MA27

2 participants