kuhar wrote: > Projects that are using llvm as submodules > ([circt](https://github.com/llvm/circt) and > [carbon-lang](https://github.com/carbon-language/carbon-lang/tree/trunk) are > places where I hit this) before this commit will need to either wait until > they're past this commit to use it directly, or will need to use the older > type first and then update again when updating LLVM. > > Can we consider aliasing `llvm::detail::scope_exit` to `llvm::scope_exit` to > enable easier and more expedient migrations? I'm happy to send a PR.
In general, we don't guarantee API/ABI stability for ADT/Support libraries. We certainly don't want to make downstream's live difficult, but this seems like a very straightforward thing to upgrade -- just `s/detail::scope_exit/scope_exit/` when you bump the llvm submodule. https://github.com/llvm/llvm-project/pull/173131 _______________________________________________ lldb-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
