Skip to content
This repository was archived by the owner on May 7, 2021. It is now read-only.

Conversation

@avieth
Copy link
Contributor

@avieth avieth commented Mar 29, 2020

This can be useful when, for instance, you want to give a header file to a developer who doesn't care that you generated your C from copilot.

@avieth
Copy link
Contributor Author

avieth commented Mar 29, 2020

@fdedden
Copy link
Member

fdedden commented Mar 30, 2020

Thanks for your suggestion. Although Copilot is mainly designed to hook into already defined C functions, being able to specify names for these arguments will never hurt, and make the written code more self-explanatory.

Traceability (that is being able to trace parts of the output C to the original Haskell definition) is very much related to this issue, and something we want to improve in the future. Giving names to arguments (or preferably streams in general) would definitely aid in this.

I will discuss your idea with the other maintainers in our next meeting.

@fdedden fdedden added the feature request Request or advice for a feature label Mar 31, 2020
@fdedden
Copy link
Member

fdedden commented Apr 7, 2020

During our most recent meeting, we discussed the idea of having named arguments and your approach. We like the idea of being able to give names to arguments, but we really prefer this to be a thing for streams, and not just trigger arguments. We decided that we want to look for a solution binds names to streams.

I will close this pull request for now, and move the (possible) discussion to a new issue which will refer to this pull request.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

feature request Request or advice for a feature

Development

Successfully merging this pull request may close these issues.

2 participants