diff options
author | James McCoy <jamessan@jamessan.com> | 2020-09-20 11:30:20 -0400 |
---|---|---|
committer | James McCoy <jamessan@jamessan.com> | 2020-09-20 11:45:56 -0400 |
commit | 461c18edad41a2ab3301f40b4b2f240d9662800d (patch) | |
tree | cefd9b610818264013d468742aaae0c1a344ac13 /runtime/lua/vim/lsp/rpc.lua | |
parent | 9f704c88a57cfb797c21c19672ea6617e9673360 (diff) | |
download | rneovim-461c18edad41a2ab3301f40b4b2f240d9662800d.tar.gz rneovim-461c18edad41a2ab3301f40b4b2f240d9662800d.tar.bz2 rneovim-461c18edad41a2ab3301f40b4b2f240d9662800d.zip |
Only use __has_include when it is defined
Per GCC's documentation:
> The __has_include operator by itself, without any operand or parentheses, acts as a predefined macro so that support for it can be tested in portable code. Thus, the recommended use of the operator is as follows:
>
> #if defined __has_include
> # if __has_include (<stdatomic.h>)
> # include <stdatomic.h>
> # endif
> #endif
>
> The first ‘#if’ test succeeds only when the operator is supported by the version of GCC (or another compiler) being used. Only when that test succeeds is it valid to use __has_include as a preprocessor operator.
Diffstat (limited to 'runtime/lua/vim/lsp/rpc.lua')
0 files changed, 0 insertions, 0 deletions