digitalmars.D - Do you want support for CTFE coverage ?
- Stefan Koch (7/7) Jul 01 2016 Hi,
- ketmar (7/7) Jul 01 2016 there is no need in that, absolutely. CTFE is undebugabble anyway
- Walter Bright (3/4) Jul 01 2016 It's not necessary since CTFE code can all be executed at runtime, and c...
- Stefan Koch (3/7) Jul 01 2016 Fair enough :)
- Basile B. (5/13) Jul 01 2016 What I'd like is that the code inside 'if(__ctfe)' branches gets
Hi, Exactly as per title. Do you want to see coverage for code executed at CTFE ? I ask because it is slightly tricky to support this and it needs to be factored in early in design. And please off-topic or thread hijacking this time. Thanks!
Jul 01 2016
there is no need in that, absolutely. CTFE is undebugabble anyway (and pragma(msg) not really helps -- i'm saying that as a fan of printf debugger), unittesting it is silly and so on. after all, as CTFE *should* behave the same if it is done in runtime, one can always test and debug CTFE code as "normal" code before using. so, i say: "don't bother".
Jul 01 2016
On 7/1/2016 1:29 PM, Stefan Koch wrote:Do you want to see coverage for code executed at CTFE ?It's not necessary since CTFE code can all be executed at runtime, and coverage tested that way.
Jul 01 2016
On Saturday, 2 July 2016 at 00:34:05 UTC, Walter Bright wrote:On 7/1/2016 1:29 PM, Stefan Koch wrote:Fair enough :) execpt for code guarded by if (__ctfe)Do you want to see coverage for code executed at CTFE ?It's not necessary since CTFE code can all be executed at runtime, and coverage tested that way.
Jul 01 2016
On Saturday, 2 July 2016 at 00:38:56 UTC, Stefan Koch wrote:On Saturday, 2 July 2016 at 00:34:05 UTC, Walter Bright wrote:What I'd like is that the code inside 'if(__ctfe)' branches gets ignored in the coverage results, so that 100% can be reached. for normal CTFE, to use assert() instead of static assert() does the trick.On 7/1/2016 1:29 PM, Stefan Koch wrote:Fair enough :) execpt for code guarded by if (__ctfe)Do you want to see coverage for code executed at CTFE ?It's not necessary since CTFE code can all be executed at runtime, and coverage tested that way.
Jul 01 2016