https://issues.dlang.org/show_bug.cgi?id=14855
Basile-z changed:
What|Removed |Added
CC||b2.t...@gmx.com
Resolution|WORKSFORME
https://issues.dlang.org/show_bug.cgi?id=14855
Luís Ferreira changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
https://issues.dlang.org/show_bug.cgi?id=14855
--- Comment #7 from hst...@quickfur.ath.cx ---
To me it doesn't make sense that `assert(0);` should be counted towards
coverage. I mean, `assert(0);` is basically the programmer telling the
compiler "this is not supposed to happen" and "this is
https://issues.dlang.org/show_bug.cgi?id=14855
hst...@quickfur.ath.cx changed:
What|Removed |Added
CC||hst...@quickfur.ath.cx
--
https://issues.dlang.org/show_bug.cgi?id=14855
Iain Buclaw changed:
What|Removed |Added
CC||ibuc...@gdcproject.org
https://issues.dlang.org/show_bug.cgi?id=14855
--- Comment #5 from Jonathan M Davis ---
> Maybe we can add a compiler flag or API in Druntime to change the behavior
> based on a user's opinion?
Much as I would love to see assert(0) not counted towards the
https://issues.dlang.org/show_bug.cgi?id=14855
greensunn...@gmail.com changed:
What|Removed |Added
CC||greensunn...@gmail.com
--- Comment
https://issues.dlang.org/show_bug.cgi?id=14855
--- Comment #3 from Jonathan M Davis ---
(In reply to Walter Bright from comment #2)
> Being concerned about assert(0)'s not being executed is placing too
> much emphasis on the metric.
Perhaps, but if you're trying to
https://issues.dlang.org/show_bug.cgi?id=14855
Walter Bright changed:
What|Removed |Added
CC|
https://issues.dlang.org/show_bug.cgi?id=14855
Jonathan M Davis changed:
What|Removed |Added
CC|
10 matches
Mail list logo