forbidden-apis VS NullAway

> All this stuff would be a lot easier if timezones always had to be stated explicitly.

On Java, you can use the forbidden-apis build plugin (https://github.com/policeman-tools/forbidden-apis) to fail the build whenever a timezone or locale or charset is not specified explicitly (it forbids the methods from the Java API which use an implicit timezone/locale/charset). I don't know whether there's something similar for Python; it might be harder because Python is much more dynamic (though it might be possible to use monkeypatching to warn whenever the bad methods are used).

Is https://github.com/policeman-tools/forbidden-apis something that might help you in the interim?

Besides the classic pmd/stopbugs/jacoco/owasp, a favorite of mine is forbidden-apis.

Regarding the "deleting them if not necessary any or are deprecated or do not make sense anymore ", something you can use today is this nice maven plugin:forbidden-apis.

Some patterns arise from language design

* You can't express `T` where `null` is forbidden in the type system so you get NullPointerException everywhere and defensive null checks.

* You express a sum type as a product type because your language does not have sum types .

* Your language doesn't have first class multiple return values (or tuples) so you return extra parameters via out parameters or thread local variables such as `errno`.

* Your language doesn't have exceptions (or algebraic effects) and can't do IO so you have monad transformers.

* Your language doesn't have set-theoretic types so you need hacks like `thiserror` .

* Your language doesn't have stackful coroutines or can't infer async IO for you so you have `async/await` spam or callback hell or "mono's".

* Your language doesn't have exhaustive checks (or pattern matching) so you need a fallthrough case check on switch statements .

* Your language doesn't have algebraic effects, so you need to pass context everywhere.

I know someone will reply about Java's null annotation checking options, so here is one of them: https://github.com/uber/NullAway .

If you must use Java, use Uber's Nullaway which gives null safety via Errorprone.

Does anyone have experience using this at Meta who can compare to https://github.com/uber/NullAway ?

A special kind of validation is enforcing that record fields are not null. (Un)fortunately, records do not have any special behavior regarding nullability. You can use tools like NullAway or Error Prone to prevent null in your code in general, or you can add checks to your records:

What do you think of https://github.com/uber/NullAway

Take a look at NullAway, a plugin for Error Prone.

PMD, Spotbugs, Nullaway: Java linting/static analysis (https://pmd.github.io, https://spotbugs.github.io, https://github.com/uber/NullAway)

In personal projects, I've had good experiences using the error-prone compiler plugin with uber's nullaway.