search for: globpattern

Yes definitely, testing a small piece of code like the GlobPattern::create() example, it would mostly indicate missing unit tests or insufficient test data. In contrast to unit tests, however, it can also verify correct handling of errors passed between function call hierarchies in more complex scenarios. For this I should point to the other example in the code,...

...g logic. Cheers, Lang. On Thu, Jul 27, 2017 at 8:56 AM, David Blaikie <dblaikie at gmail.com> wrote: > > > On Thu, Jul 27, 2017 at 8:54 AM Stefan Gränitz <stefan.graenitz at gmail.com> > wrote: > >> Yes definitely, testing a small piece of code like the >> GlobPattern::create() example, it would mostly indicate missing unit tests >> or insufficient test data. >> >> In contrast to unit tests, however, it can also verify correct handling >> of errors passed between function call hierarchies in more complex >> scenarios. >> For t...

Hello, this is a call for feedback: opinions, improvements, testers.. I use the support classes Expected<T> and ErrorOr<T> quite often recently and I like the concept a lot! Thanks Lang btw! However, from time to time I found issues in the execution paths of my error cases and got annoyed by their naturally low test coverage. So I started sketching a test that runs all error paths

..., Jul 27, 2017 at 8:56 AM, David Blaikie <dblaikie at gmail.com> wrote: > >> >> >> On Thu, Jul 27, 2017 at 8:54 AM Stefan Gränitz <stefan.graenitz at gmail.com> >> wrote: >> >>> Yes definitely, testing a small piece of code like the >>> GlobPattern::create() example, it would mostly indicate missing unit tests >>> or insufficient test data. >>> >>> In contrast to unit tests, however, it can also verify correct handling >>> of errors passed between function call hierarchies in more complex >>> scena...

2017-05-26 17:47 GMT-07:00 Zachary Turner via llvm-dev < llvm-dev at lists.llvm.org>: > Changing a header file somewhere and having to spend 10 minutes waiting > for a build leads to a lot of wasted developer time. > > The real culprit here is tablegen. Can we split support and ADT into two > - the parts that tablegen depends on and the parts that it doesn't? >

...ommandLine.h > Compiler.h > ConvertUTF.h > CrashRecoveryContext.h > DataExtractor.h > Debug.h > Endian.h > EndianStream.h > Errc.h > Errno.h > Error.h > ErrorHandling.h > ErrorOr.h > FileOutputBuffer.h > FileSystem.h > FileUtilities.h > Format*.h > GlobPattern.h > Host.h > JamCRC.h > KnownBits.h > LineIterator.h > Locale.h > ManagedStatic.h > MathExtras.h > MD5.h > Memory.h > MemoryBuffer.h > Mutex.h > MutexGuard.h > NativeFormatting.h > Options.h > Parallel.h > Path.h > PointerLikeTypeTraits.h > Pret...

...ws.llvm.org/rL290284). * A POWER9 processor model was added for scheduling. [r290102](http://reviews.llvm.org/rL290102). * ARM and PPC support has been added to the `update_llc_test_checks.py` script. [r290144](http://reviews.llvm.org/rL290144), [r290370](http://reviews.llvm.org/rL290370). * The GlobPattern class has been imported into LLVM from LLD. [r290212](http://reviews.llvm.org/rL290212). * Codegen for the x86 vectorcall calling convention has landed. [r290240](http://reviews.llvm.org/rL290240). ## Clang commits * It is now possible to use the (still experimental) new pass manager with Clang...

...ommandLine.h > Compiler.h > ConvertUTF.h > CrashRecoveryContext.h > DataExtractor.h > Debug.h > Endian.h > EndianStream.h > Errc.h > Errno.h > Error.h > ErrorHandling.h > ErrorOr.h > FileOutputBuffer.h > FileSystem.h > FileUtilities.h > Format*.h > GlobPattern.h > Host.h > JamCRC.h > KnownBits.h > LineIterator.h > Locale.h > ManagedStatic.h > MathExtras.h > MD5.h > Memory.h > MemoryBuffer.h > Mutex.h > MutexGuard.h > NativeFormatting.h > Options.h > Parallel.h > Path.h > PointerLikeTypeTraits.h > Pret...