Buoyant VS Error Prone

At my day job (https://buoyant.io/), we're using it to write a reverse proxy/load balancer --- one of the use-cases where you really, absolutely do need asynchronous concurrency. :). - Source: Hacker News / over 2 years ago

Not to be confused with the other Buoyant [1], the company behind the linkerd service mesh. Not that I'm really into service meshes, but I happened to be doing some reading about the Tokio async runtime for Rust yesterday, and a lot of the work on that has been funded by that Buoyant, which is why that company was on my mind. [1]: https://buoyant.io/. - Source: Hacker News / over 2 years ago

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:. - Source: dev.to / over 1 year ago

I am all in favour to more third side libraries adding functionalities, like Lombok, Manifold and error prone. As well as smaller projects like this shameless plug and what appears in this list. Source: over 1 year ago

While at it you could also point them to static code analyzers such as error_prone, spotbugs and pmd (use all 3 at once - they complement each other in detecting different issues). Source: over 2 years ago

Linters can check for this sort of thing, for example Error Prone[0] has a lint[1] for this. Totally agree this is better to be in the language proper so we don't need this extra tooling. [0]: https://errorprone.info [1]: https://errorprone.info/bugpattern/ParameterName. - Source: Hacker News / over 2 years ago