CODEWITHSUNDEEP
javajvmassert
Sundarram P.V.
Sundarram P.V.

Reputation: 359

Why is assert not enabled by default in java

My question is from the perspective of language design.

Why is assert treated differently i.e. it raises a error and not an exception, it is not enabled by default etc..

It does seem elegant(very subjective opinion), easy to read(again subjective) for doing validations & also there are tools(IDE) which can live-evaluate it and provide warnings based on assertions.

Upvotes: 15

Views: 7191

Answers (3)

Mateusz Kubuszok
Mateusz Kubuszok

Reputation: 27605

I'd say that the reason is that defaults for Java are meant for production code (the "release" version of software) - if users need to build your code they will use provided defaults and if you are developer and want to have better reporting you can always make some additional effort.

Usually you don't want to ship assertions with a release version. Why? You can always design your code to perform some not disturbing background error handling and throwing AssertionError in users face is not always the way to go.

Most of the time I see them used as additional code testing - when you run regression tests and code coverage is high no assertion error suggest that there are no (obvious to spot) errors in your code. If some happens, you can deduce from stack trace what went wrong and why. On the other hand clients shouldn't be bothered with seeing descriptive error information.

So how should you actually use them? In my experience you should design code to not use assertions to perform error handling. If you want exception to be thrown somewhere throw it explicitly yourself. Once code can handle itself, you can add assertions to check pre- and postconditions as well as invariants - so basically used them to check algorithm correctness instead of data correctness. It has value for developers rather than users. Once you have enough confidence in your solution, you can disable assertions, your program still works fine and your users don't have to run program with additional runtime overhead.

Upvotes: 10

Ray
Ray

Reputation: 41508

Asserts are tools for the developer.

The core reason it's not enabled by default is that assertions via assert are not meant to provide run-time validation/protection for production code.

assert is a tool for use in development process and during testing that should not impact performance during actual running in production environment.

Imagine a very heavy weight assertions that are critical to check when building out a new feature or a change against a entire range of allowable inputs, but once built and properly tested, don't need to run until code changes again.

Upvotes: 7

UniversE
UniversE

Reputation: 2506

It raises an error, because the severity of an assertion violation is high enough to do so.

An example for an Exception is something like ArrayIndexOutOfBounds. This might be reasonable in some cases and you might even expect (and handle) such a case.

But an assertion violation is (like out of memory e.g.) nothing you would ever expect or you would like to deal with. It's an error and there is no excuse.

Assertions are not enabled by default, because they should be always fullfilled. You enable them to test for that, but then you "know" (as far as you can know) that they are not violated. So you don't need to check the conditions (which might be performance intensive) every time in production code.

The good thing about assertions in Java is, that the code actually performing the checks is never executed, when assertions are not enabled.

For example:

if (!doComplexChecks()) throw new AssertionError("Damn!");

might take a lot of time and you want to verify this when unit testing or debugging, but in production you just don't want that.

But this code

assert doComplexChecks();

is only executed, when assertions are enabled, so it saves you a lot of time in production code.

Upvotes: -1

Related Questions