[Swift-devel] assertion behavior

[Michael Wilde]

Does "terminate immediately" need to always be immediate or should/could 
it integrate with the Swift/K notion of "soft errors"?

I.e. an assert failure is treated like a failing function; that in turn 
as handled as the soft-error property specifies.
- Mike


On 3/25/15 10:24 PM, Tim Armstrong wrote:
> The program terminates immediately with an error message.
>
> There's a compile-time option to disable assertions if needed.  It's 
> actually a little weird in that it syntactically removes the statement 
> - it doesn't evaluate the arguments to the funciton.
>
> - Tim
>
> On 25 March 2015 at 22:09, Mihael Hategan <hategan at mcs.anl.gov 
> <mailto:hategan at mcs.anl.gov>> wrote:
>
>     Hi,
>
>     In Swift/T, what happens when an assertion fails?
>
>     Mihael
>
>     _______________________________________________
>     Swift-devel mailing list
>     Swift-devel at ci.uchicago.edu <mailto:Swift-devel at ci.uchicago.edu>
>     https://lists.ci.uchicago.edu/cgi-bin/mailman/listinfo/swift-devel
>
>
>
>
> _______________________________________________
> Swift-devel mailing list
> Swift-devel at ci.uchicago.edu
> https://lists.ci.uchicago.edu/cgi-bin/mailman/listinfo/swift-devel

-- 
Michael Wilde
Mathematics and Computer Science          Computation Institute
Argonne National Laboratory               The University of Chicago

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/swift-devel/attachments/20150327/25054ab1/attachment.html>