-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
API docs #7814
Comments
Managing expectations around these docs is going to be key. A lot of what they document is internal and subject to change, but that does not mean that we shouldn't improve their documentation. |
Triaged in the Nix team meeting 2023-02-17:
|
This issue has been mentioned on NixOS Discourse. There might be relevant details there: https://discourse.nixos.org/t/2023-02-17-nix-team-meeting-minutes-33/25624/1 |
The motivation is as stated in issue NixOS#7814: even though the the C++ API is internal and unstable, people still want it to be well documented for sake of learning, code review, and other purposes that aren't predicated on it being stable. Fixes NixOS#7814
The motivation is as stated in issue NixOS#7814: even though the the C++ API is internal and unstable, people still want it to be well documented for sake of learning, code review, and other purposes that aren't predicated on it being stable. Fixes NixOS#7814
The motivation is as stated in issue NixOS#7814: even though the the C++ API is internal and unstable, people still want it to be well documented for sake of learning, code review, and other purposes that aren't predicated on it being stable. Fixes NixOS#7814
The motivation is as stated in issue NixOS#7814: even though the the C++ API is internal and unstable, people still want it to be well documented for sake of learning, code review, and other purposes that aren't predicated on it being stable. Fixes NixOS#7814 Co-authored-by: Robert Hensing <[email protected]>
The motivation is as stated in issue NixOS#7814: even though the the C++ API is internal and unstable, people still want it to be well documented for sake of learning, code review, and other purposes that aren't predicated on it being stable. Fixes NixOS#7814 Co-authored-by: Robert Hensing <[email protected]>
The motivation is as stated in issue NixOS#7814: even though the the C++ API is internal and unstable, people still want it to be well documented for sake of learning, code review, and other purposes that aren't predicated on it being stable. Fixes NixOS#7814 Co-authored-by: Robert Hensing <[email protected]>
The motivation is as stated in issue NixOS#7814: even though the the C++ API is internal and unstable, people still want it to be well documented for sake of learning, code review, and other purposes that aren't predicated on it being stable. Fixes NixOS#7814 Co-authored-by: Robert Hensing <[email protected]>
For the record, https://hydra.nixos.org/build/224134462#tabs-summary is an example. |
It would be good for have API docs generated from comments in the C++ source.
Even though the internal Nix library APIs are unstable and therefore not intended for large scale outside consumption, contributers to Nix itself would still benefit.
Also, in conjunction with stable bindings to other languages, we've discussed stabilizing parts of the C++ interfaces. This would naturally be good for that.
The text was updated successfully, but these errors were encountered: