kevin/neovim
1
Fork 0
mirror of https://github.com/neovim/neovim.git synced 2024-12-25 05:35:10 -07:00
Code Issues Packages Projects Releases Wiki Activity

fix code block

dundargoc 2023-10-07 11:32:22 +02:00
parent cc9ef90068
commit 3b817e9f26
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
C-type-refactoring-guidelines.md

@ -38,7 +38,7 @@ We should try to keep structs small, if possible. To that end:
#### External interfaces #### External interfaces
- For functions interfacing other processes over a transport/serialization mechanism, fixed-width types are preferred. For example, in `msgpack_rpc.h`: - For functions interfacing other processes over a transport/serialization mechanism, fixed-width types are preferred. For example, in `msgpack_rpc.h`:
```c ```c
bool msgpack_rpc_integer_result(uint32_t result, bool msgpack_rpc_integer_result(uint32_t result,
msgpack_object *req, msgpack_object *req,
msgpack_packer *res); msgpack_packer *res);
@ -46,7 +46,7 @@ bool msgpack_rpc_integer_result(uint32_t result,
- For functions part of a public API, native types are preferred. For example, in a hypothetical `libneovim.h`: - For functions part of a public API, native types are preferred. For example, in a hypothetical `libneovim.h`:
```c ```c
int neovim_get_current_buffer(void); int neovim_get_current_buffer(void);
``` ```