WriteAccessors prefers 'later' candidates to earlier ones?

On this line, why does it prefer to overwrite the existing candidate if it has found one? It seems somewhat arbitrary.

https://github.com/mapstruct/mapstruct/blob/1ab5db6a2774a58a6c41b5e4c2bfb23b2fa1bab7/processor/src/main/java/org/mapstruct/ap/internal/model/common/Type.java#L806

I guess the particular reason I'm asking is that when it is mapping to Immutable.Builders, it finds both the 'normal' setter and the one that accepts an Optional, and it prefers the Optional because it comes later in the candidate list, even though the 'normal' setter would be marginally more efficient - and wouldn't require me to define loads of

Optional<? extends MyClass> toOptional(MyClass x)

methods. The Builders have no readAccessors unfortunately, so it can only really match on the propertyName and is unable to determine the 'preferredType'. This is when a custom SPI is in use btw (the protobuf one), so it isn't using ImmutablesAccessorNamingStrategy though from a brief look that wouldn't make a difference anyway.

Bắt đầu tại dòng 806 của processor/src/main/java/org/mapstruct/ap/internal/model/common/Type.java và theo dõi cách các ứng viên WriteAccessors được thay thế. Tái hiện ánh xạ Immutable.Builder bằng protobuf custom SPI, đồng thời so sánh các setter thông thường với các setter Optional. Khi hoàn tất, việc chọn ứng viên phải có chủ đích thay vì phụ thuộc vào thứ tự danh sách, kèm theo coverage cho trường hợp này.