On Sunday, 27 August 2017 at 10:46:53 UTC, Andrew Chapman wrote:
[...]
Oh interesting. Does DUB support passing through the
--enable-contracts flag to ldc? Also, if this is an ldc
specific thing it's probably not a good idea i'd imagine, since
in the future one may want to use a GDC, or
On Sunday, 27 August 2017 at 10:46:53 UTC, Andrew Chapman wrote:
On Sunday, 27 August 2017 at 10:37:50 UTC, Moritz Maxeiner
wrote:
[...]
Oh interesting. Does DUB support passing through the
--enable-contracts flag to ldc?
Sure, using platform specific build settings [1] such as
On Sunday, 27 August 2017 at 10:37:50 UTC, Moritz Maxeiner wrote:
On Sunday, 27 August 2017 at 10:17:47 UTC, Andrew Chapman wrote:
On Sunday, 27 August 2017 at 10:08:15 UTC, ag0aep6g wrote:
[...]
Thanks, that explains it. I think it's a bit of a shame that
the "in" blocks can't be used in
On Sunday, 27 August 2017 at 10:17:47 UTC, Andrew Chapman wrote:
On Sunday, 27 August 2017 at 10:08:15 UTC, ag0aep6g wrote:
On 08/27/2017 12:02 PM, Andrew Chapman wrote:
However, I am finding that BOTH enforce and assert are
compiled out by dmd and ldc in release mode. Is there a
standard
On Sunday, 27 August 2017 at 10:08:15 UTC, ag0aep6g wrote:
On 08/27/2017 12:02 PM, Andrew Chapman wrote:
However, I am finding that BOTH enforce and assert are
compiled out by dmd and ldc in release mode. Is there a
standard way of doing what enforce does inside an "in"
contract block that
On 08/27/2017 12:02 PM, Andrew Chapman wrote:
However, I am finding that BOTH enforce and assert are compiled out by
dmd and ldc in release mode. Is there a standard way of doing what
enforce does inside an "in" contract block that will work in release mode?
I'm guessing I should write my
In the docs regarding contract programming and the use of enforce
/ assert:
https://dlang.org/library/std/exception/enforce.html
it says:
"enforce is used to throw exceptions and is therefore intended to
aid in error handling. It is not intended for verifying the logic
of your program. That
