[llvm] [HLSL] Analyze update counter usage (PR #130356)

[via llvm-commits]

================
@@ -407,6 +411,77 @@ class DXILResourceTypeMap {
   }
 };
 
+enum ResourceCounterDirection {
+  Increment,
+  Decrement,
+  Unknown,
+};
+
+class DXILResourceCounterDirectionMap {
+  std::vector<std::pair<dxil::ResourceBindingInfo, ResourceCounterDirection>>
----------------
joaosaffran wrote:

nit: Why using a vector instead of map or set like instruction? The code seems to be performing some deduplication and validation logic after checking all uses. I feel like there might be some other structure that can be used to make this simpler. Here is a [link](https://llvm.org/docs/ProgrammersManual.html#picking-the-right-data-structure-for-a-task) to a list of structures available in llvm, in case you don't have it already.

https://github.com/llvm/llvm-project/pull/130356