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
Prepare ctypes 0.9.2 #444
Prepare ctypes 0.9.2 #444
Conversation
Would you mind having a look at |
|
I'm not sure that the errors are fixable, unfortunately: the problems are with references to internal modules for which the |
Ok but are these interfaces supposed to be used by end-users ? If not you could avoid installing them. FWIW here's the current rendering you get with |
In general |
The difficulty arises with modules whose types need to be exposed so that generated code can be type-checked but that are not intended to be used directly by end users. It sounds like the best thing is to install only |
Note that eventually I plan to add OPAMv2 directives to be specified in your package file to guide a bit what |
Just one question about about the changes you made to |
The changes make sense from an API point of view. It seems unreasonable to expose functions in the public interface if those function have types whose names aren't also exposed. So I changed the type of |
Ok thanks. |
No description provided.