Hello Vincent,
I would appreciate some clarification on a few points to ensure my plan aligns with the project’s goals and community standards. 1. *Mapping gfun Functions:* Could you provide guidance on which gfun functions should be prioritized for the interface? Are there specific functions or features that are most critical for an initial implementation? 2. *Interface to the C-library flint:* Regarding the integration with flint, should the focus be on developing a lightweight wrapper around existing flint functionality, or is there an expectation to modify or extend flint’s capabilities within SageMath? 3. *Documentation Requirements:* The proposal mentions the need for documentation explaining how each gfun function call can be replaced by standard SageMath computations. Are there any preferred formats or guidelines (e.g., examples, benchmarks) that you would recommend following? 4. *Additional Features and Benchmarks:* Would it be beneficial to include performance benchmarks or comparisons in the proposal to demonstrate the advantages of the new interface over current implementations? Or should the emphasis be more on achieving a standardized and user-friendly interface? Thank you very much for your time and any insights you can provide. Best regards, -- You received this message because you are subscribed to the Google Groups "sage-gsoc" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-gsoc+unsubscr...@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/sage-gsoc/58a948d9-ab12-4028-a8dc-e50b8f9558efn%40googlegroups.com.
