A default order on Values allows for its use in, e.g.,
llvm::EquivalenceClasses.
Details
Details
Diff Detail
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
Comment Actions
This order won't be stable between runs though, so any test depends on the ordering would be flaky. Why not add a simple wrapper class locally where you need this? Keeps it local to where the ordering doesn't matter and avoids folks accidentally relying on it accidentally.
Comment Actions
I typically use getAsOpaquePointer() to get a void* and then place that in the collection at hands. That is unstable too but only locally where the context is clear.