search for: driectly

...ally the intention of the FileManager to allow doing the things we do with it: not every module in clang uses the FileManager, and the moment we hit llvm there is no FileManager at all. For example, in case of the Driver we hack around the fact that the header search tries to access the file system driectly in rather brittle ways, relying on implementation details and #ifdefs. So why not make FileManager a more principled (and still blazing fast) file system abstraction? Pro: - only one interface for developers to learn on the project (no more PathV1 vs PathV2 vs FileManager) - only one implementatio...

...> FileManager to allow doing the things we do with it: not every module > in clang uses the FileManager, and the moment we hit llvm there is no > FileManager at all. For example, in case of the Driver we hack around > the fact that the header search tries to access the file system > driectly in rather brittle ways, relying on implementation details and > #ifdefs. > > So why not make FileManager a more principled (and still blazing fast) > file system abstraction? > Pro: > - only one interface for developers to learn on the project (no more > PathV1 vs PathV2 vs Fil...

...r to allow doing the things we do with it: not every module >> in clang uses the FileManager, and the moment we hit llvm there is no >> FileManager at all. For example, in case of the Driver we hack around >> the fact that the header search tries to access the file system >> driectly in rather brittle ways, relying on implementation details and >> #ifdefs. >> >> So why not make FileManager a more principled (and still blazing fast) >> file system abstraction? > > Yes, please! Great :) /me jumps right into the design discussion then. > Having a...

...> FileManager to allow doing the things we do with it: not every module > in clang uses the FileManager, and the moment we hit llvm there is no > FileManager at all. For example, in case of the Driver we hack around > the fact that the header search tries to access the file system > driectly in rather brittle ways, relying on implementation details and > #ifdefs. > > So why not make FileManager a more principled (and still blazing fast) > file system abstraction? Yes, please! Having a proper virtual file system across Clang and LLVM would be a huge boon, especially for p...

...r to allow doing the things we do with it: not every module >> in clang uses the FileManager, and the moment we hit llvm there is no >> FileManager at all. For example, in case of the Driver we hack around >> the fact that the header search tries to access the file system >> driectly in rather brittle ways, relying on implementation details and >> #ifdefs. >> >> So why not make FileManager a more principled (and still blazing fast) >> file system abstraction? >> Pro: >> - only one interface for developers to learn on the project (no more >...

...the things we do with it: not every module >>> in clang uses the FileManager, and the moment we hit llvm there is no >>> FileManager at all. For example, in case of the Driver we hack around >>> the fact that the header search tries to access the file system >>> driectly in rather brittle ways, relying on implementation details and >>> #ifdefs. >>> >>> So why not make FileManager a more principled (and still blazing fast) >>> file system abstraction? >> >> Yes, please! > > Great :) /me jumps right into the desig...

...o with it: not every module >>>> in clang uses the FileManager, and the moment we hit llvm there is no >>>> FileManager at all. For example, in case of the Driver we hack around >>>> the fact that the header search tries to access the file system >>>> driectly in rather brittle ways, relying on implementation details and >>>> #ifdefs. >>>> >>>> So why not make FileManager a more principled (and still blazing fast) >>>> file system abstraction? >>> >>> Yes, please! >> >> Grea...

...the things we do with it: not every module >>> in clang uses the FileManager, and the moment we hit llvm there is no >>> FileManager at all. For example, in case of the Driver we hack around >>> the fact that the header search tries to access the file system >>> driectly in rather brittle ways, relying on implementation details and >>> #ifdefs. >>> >>> So why not make FileManager a more principled (and still blazing fast) >>> file system abstraction? >>> Pro: >>> - only one interface for developers to learn on t...

...very module >>>>> in clang uses the FileManager, and the moment we hit llvm there is no >>>>> FileManager at all. For example, in case of the Driver we hack around >>>>> the fact that the header search tries to access the file system >>>>> driectly in rather brittle ways, relying on implementation details and >>>>> #ifdefs. >>>>> >>>>> So why not make FileManager a more principled (and still blazing fast) >>>>> file system abstraction? >>>> >>>> Yes, please! &...

...the things we do with it: not every module >>> in clang uses the FileManager, and the moment we hit llvm there is no >>> FileManager at all. For example, in case of the Driver we hack around >>> the fact that the header search tries to access the file system >>> driectly in rather brittle ways, relying on implementation details and >>> #ifdefs. >>> >>> So why not make FileManager a more principled (and still blazing fast) >>> file system abstraction? >> >> Yes, please! > > Great :) /me jumps right into the desig...

...o with it: not every module >>>> in clang uses the FileManager, and the moment we hit llvm there is no >>>> FileManager at all. For example, in case of the Driver we hack around >>>> the fact that the header search tries to access the file system >>>> driectly in rather brittle ways, relying on implementation details and >>>> #ifdefs. >>>> >>>> So why not make FileManager a more principled (and still blazing fast) >>>> file system abstraction? >>> >>> Yes, please! >> >> Great :...

...very module >>>>> in clang uses the FileManager, and the moment we hit llvm there is no >>>>> FileManager at all. For example, in case of the Driver we hack around >>>>> the fact that the header search tries to access the file system >>>>> driectly in rather brittle ways, relying on implementation details and >>>>> #ifdefs. >>>>> >>>>> So why not make FileManager a more principled (and still blazing fast) >>>>> file system abstraction? >>>> >>>> Yes, please! &...

...>>>>> in clang uses the FileManager, and the moment we hit llvm there is no >>>>>> FileManager at all. For example, in case of the Driver we hack around >>>>>> the fact that the header search tries to access the file system >>>>>> driectly in rather brittle ways, relying on implementation details and >>>>>> #ifdefs. >>>>>> >>>>>> So why not make FileManager a more principled (and still blazing fast) >>>>>> file system abstraction? >>>>> >>&gt...

...;>>>> in clang uses the FileManager, and the moment we hit llvm there is no > >>>>> FileManager at all. For example, in case of the Driver we hack around > >>>>> the fact that the header search tries to access the file system > >>>>> driectly in rather brittle ways, relying on implementation details > and > >>>>> #ifdefs. > >>>>> > >>>>> So why not make FileManager a more principled (and still blazing > fast) > >>>>> file system abstraction? > >>>&...