anchor.diff:  include::sample[dir="snippets/dependencyManagement/catalogs-settings/kotlin",files="build.gradle.kts[tags=use_catalog]"]
   ====
   
  -is **strictly equivalent** to writing:
  +...has **exactly the same** effect as writing:
   
   .Dependency notation correspondance
   ====
  
positive.code: 
  Dependencies declared in a catalog are exposed to build scripts via an extension corresponding to their name.
  In the example above, because the catalog declared in settings is named `libs`, the extension is available via the name `libs` in all build scripts of the current build.
  Declaring a dependency using the following notation:
  
  .Dependency notation correspondance
  ====
  
negative.code: include::sample[dir="snippets/dependencyManagement/catalogs-settings/kotlin",files="settings.gradle.kts[tags=catalog_with_bundle]"]
  ====
  
  The semantics are again equivalent: adding a single bundle is equivalent to adding all dependencies which are part of the bundle individually.
  
  [[sub:conventional-dependencies-toml]]
  === The dependencies.toml file
  