Displaying 3 results from an estimated 3 matches for "hfe6470xzhk".
2011 Jul 27
0
[LLVMdev] Proposal for better assertions in LLVM
...something like this:
>
> ASSERT_STRM(Ty == STy, "Expected " << Ty << " but got " <<
> STy->getElementType(0));
>
Chromium (and several other Google open source projects) have a somewhat
superior variant of this:
http://google.com/codesearch#hfE6470xZHk/base/logging.h&exact_package=http://src.chromium.org/git/chromium.git&q=CHECK&type=cs&l=398
It ends up looking like:
CHECK(Ty == STy) << "Expected " << Ty << " .." << ...;
The important difference is that most of the parameters go outsi...
2011 Jul 26
5
[LLVMdev] Proposal for better assertions in LLVM
The assertions in LLVM would be a lot more useful if they could print out
not only the source code of the expression that failed, but also print the
values of the various arguments. To that end, I have an idea for an improved
assert macro which would use raw_ostream. It would look something like this:
ASSERT_STRM(Ty == STy, "Expected " << Ty << " but got "
2011 Jul 27
3
[LLVMdev] Proposal for better assertions in LLVM
...SSERT_STRM(Ty == STy, "Expected " << Ty << " but got " <<
>> STy->getElementType(0));
>>
>
> Chromium (and several other Google open source projects) have a somewhat
> superior variant of this:
>
>
> http://google.com/codesearch#hfE6470xZHk/base/logging.h&exact_package=http://src.chromium.org/git/chromium.git&q=CHECK&type=cs&l=398
>
> It ends up looking like:
>
> CHECK(Ty == STy) << "Expected " << Ty << " .." << ...;
>
> The important difference is that most...