Paweł Łabaj

@JanecekPetr , you can use now unmodifiable views - see #154

@JanecekPetr workaround proposal: use [AutoRecord](https://github.com/pawellabaj/auto-record) with [ARICE](https://github.com/pawellabaj/auto-record/wiki/ARICE) extension. It supports the most important (all ?) interfaces from `java.util` and `com.google.common.collect` packages. However, it requires a Guava library for generated records,...

@JanecekPetr I work on a library we using in our projects to generate records based on an interface: [auto-record](https://github.com/pawellabaj/auto-record). It generates _boiler plate_ code for a nullability checking in a...

In most cases, reference to the original collection is not being kept and collection from the record is used. Another possible solution would be to treat `java.util.LinkedHashSet` or `com.google.common.collect.ImmutableSet` in...

Introducing the _useUnmodifiableCollections_ option works for me. However, it didn't solve the issue reported here. Possibly checking for specialized interfaces like _SortedSet_, etc. (see #151 ) is the solution.

@Randgalt , I'm thinking of it. Do you consider introducing Guava as a dependency to your project?

@Randgalt have you thought about introducing a plugins/extensions mechanism? Extensions with the usage of any library could be implemented.