anchor.diff:  
   Gradle provides plugins for Visual Studio and Xcode. 
   
  -When used with the C++ plugins, Gradle will generate metadata files used by these IDEs. As much as possible, we've tried to make the IDE delegate to Gradle when compiling and linking C++ applications and libraries. 
  +When used with the C\++ plugins, Gradle will generate metadata files used by these IDEs. As much as possible, we've tried to make the IDE delegate to Gradle when compiling and linking C++ applications and libraries.
   
   JetBrains maintains a separate integration with CLion.
   
  
positive.code: 
  For a library, Gradle assumes its public headers are in `src/main/public`. Header files can be mixed into `src/main/cpp`, but these headers will be treated as private and not exposed to downstream consumers.
  
  Gradle assumes C++ source files end in `.cpp`, `.c+\+` or `.cc`. 
  
  [[cpp:declaring_dependencies]]
  == Declaring dependencies
  
negative.code: Dependencies can be declared in a similar way to other Gradle plugins, like Java, with the main difference being that the `dependencies` block is inside the `application` or `library` block.
  
  C++ applications only have `implementation` level dependencies.
  
  C++ libraries have `api` and `implementation` dependencies.
  
  Dependencies that are `implementation` only are not shared with downstream consumers. `api` dependencies form a part of the public API for a library. 
  
  