Comments on: why java records aren’t quite immutable

By: Jeanne Boyarsky

Jeanne Boyarsky — Sat, 20 Aug 2022 22:13:56 +0000

In reply to Dave. Sure. But a built in API meets needs in this case.

By: Dave

Dave — Fri, 19 Aug 2022 16:03:52 +0000

Another option would be to use an Immutable List implementation like https://www.javadoc.io/static/io.vavr/vavr/0.10.4/index.html?io/vavr/collection/List.html

By: Jeanne Boyarsky

Jeanne Boyarsky — Wed, 13 Apr 2022 12:59:05 +0000

In reply to Srdjan Mitrovic. And remember to ake an immutable copy.

By: Jeanne Boyarsky

Jeanne Boyarsky — Wed, 13 Apr 2022 12:55:50 +0000

In reply to John Morrison. Agree. Hence the need to code carefully

By: John Morrison

John Morrison — Sat, 02 Apr 2022 12:05:32 +0000

Exposing mutable state is dangerous.

By: Srdjan Mitrovic

Srdjan Mitrovic — Tue, 01 Mar 2022 13:29:00 +0000

You should use List chapters
as parameter so it would not allow you to add new chapters but you could read the chapters.

By: Jeanne Boyarsky

Jeanne Boyarsky — Sun, 01 Aug 2021 15:22:40 +0000

In reply to isopov. @isopov Good point. Fixed both. Using List.copyOf now

By: isopov

isopov — Sun, 01 Aug 2021 15:10:16 +0000

>Making the record actually be mutable
Seems to be misprint – “actually immutable” supposed?

And unfortunately this does not make record truly immutable – original chapters variable may be modified after record creation and record will be changed.