gdoenlen

I've been catching up on Advent of Code over my holiday break. I've been using it as a playground to experiment with languages outside of my comfort zone; mainly F#, C#, and Kotlin. The last problem I solved was to find valid identifiers (longs) within a range. I solved this in Kotlin using a class called Range that would tell me if other identifiers were within it. This worked, but it left me asking what this data structure would look like in each language.

Kotlin

I actually found the Kotlin implementation to be more verbose than I expected. While Kotlin supports concise method bodies which greatly help with density, the rest of the declarations require a lot more than the other implementations (except for F#). For platform compatibility you need to annotate Kotlin data classes with @JvmRecord. This tells the Kotlin compiler to generate a Java record instead of a standard POJO with getters and setters.

One surprising thing that I di

gdoenlen

These are the language features I think Java needs to solve the most of its fluidity issues.

Try as an expression

Try should be an expression much like switch. It would enable clearer try catch code.

var a = try {
    yield someFn();
} catch (SomeException ex) {
    yield default;

gdoenlen

Recently at work I was tasked to fix a bug that was occuring when a user would get assigned new roles. In our product we use roles to dictate what actions a user can do within the app. A user obtains a role either via an administrator assigning them a role or they can request a role and that request can later be approved by an administrator. Whenever a role gets assigned, the user's role requests for that role should also be approved. We have 2 main workflows where a user may be assigned a role:

1. An administrator edits the user and assigns the role to a user via the user interface.
2. An administrator can import a csv file with the user's email and their roles to be assigned.

The bug we were encountering was that in the bulk import workflow the user's requests were not getting auto approved. The product would then say the user had the role but was also requesting it. I discovered that both of the workflows were implemented individually and were both directly modifying the backing entity records. The

gdoenlen

/**
 * Selector for the `Account` entity
 */
public class AccountSelector {

    public static final AccountSelector INSTANCE = new AccountSelector();

    /**
     * Finds all accounts that are child accounts of
     * the given opportunity's account.