Searched refs:Concrete (Results 1 – 3 of 3) sorted by relevance
| /freebsd/contrib/googletest/docs/ |
| H A D | gmock_cook_book.md | 563 ### Alternative to Mocking Concrete Classes
566 order to test your code that uses such a class (let's call it `Concrete`), you
567 may be tempted to make the methods of `Concrete` virtual and then mock it.
582 interfaces": instead of talking to the `Concrete` class, your code would define
584 top of `Concrete`. In tests, you can easily mock that interface to observe how
595 * `Concrete`'s API may not fit your problem domain very well, as you may not
602 * If `Concrete`'s implementation ever has to change, you don't have to rewrite
611 * Different projects may need to use `Concrete` in different ways, so the best
613 own domain-specific interface on top of `Concrete`, and they will not be the
616 just like they have been sharing `Concrete`. You can check in the interface
[all …]
|
| /freebsd/contrib/llvm-project/llvm/lib/Target/DirectX/ |
| H A D | DXIL.td | 229 // Concrete records for various overload types supported specifically by
257 // Concrete definition of DXIL Operation mapping to corresponding LLVM intrinsic
|
| /freebsd/contrib/llvm-project/clang/lib/StaticAnalyzer/Core/ |
| H A D | RegionStore.cpp | 946 const SubRegion *Concrete = TopKey.getConcreteOffsetRegion(); in removeSubRegionBindings() local
947 return B.addBinding(Concrete, BindingKey::Default, UnknownVal()); in removeSubRegionBindings()
965 const SubRegion *Concrete = TopKey.getConcreteOffsetRegion(); in removeSubRegionBindings() local
966 Result = Result.add(BindingKey::Make(Concrete, BindingKey::Default), in removeSubRegionBindings()
|