search for: realf

.... Most likely yes because of LLDB's design that abstracts over flies without prior knowledge about whether they'd only get read or written. However wouldn't it suffer form the exact same problems? > In case: > - there is a real path behind the file --- you could spawn an llvm::RealFileSystem (the fqdn might not be this after the migration patch!) and use that to obtain the file's buffer. I'm not sure I follow what you have in mind here. Can you give a little more detail? > How can you be sure the file actually exists on the FS? That's what the VFS should be al...

I'd like to get some more perspectives on the role of the VirtualFileSystem abstraction in llvm/Support. (The VFS layer has recently moved from Clang to LLVM, so crossposting to both lists) https://reviews.llvm.org/D54277 proposed adding a function to VirtualFileSystem to get the underlying "real file" path from a VFS path. LLDB is starting to use VFS for some filesystem