Proposal: Make WellKnownMutability customizable via compiler args
See original GitHub issueWe have internal clones of guava’s immutable collections (android, we don’t want the full library packaged). The result though is that some of our autovalue classes using them can’t be denoted as @Immutable
because it only looks for guava’s. It would be ideal if this could be more customizable. Thoughts?
Issue Analytics
- State:
- Created 7 years ago
- Comments:17 (6 by maintainers)
Top Results From Across the Web
Building applications with Maven - Quarkus
To do this you must build a mutable application, using the mutable-jar format. ... If you need to customize the compiler flags used...
Read more >Good uses for mutable function argument default values?
I regularly write custom functions and layers for TensorFlow/Keras, ... of good uses for mutable default argument values, I offer the following example:....
Read more >If immutable objects are good, why do people keep creating ...
Most developers create mutable objects because mutability is the default in ... Using mutable objects with immutable identities avoids that problem.
Read more >JUnit 5 User Guide
First-class support for the JUnit Platform also exists in popular IDEs ... can create a custom composed annotation named @Fast as follows.
Read more >There's Waldo! – Botond's ramblings about programming ...
This looks to me like a thorough, well-researched proposal which addresses the concerns raised during discussions of previous proposals for named arguments ( ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@epmjohnston is actively working on this in #524.
I think supporting custom
@Immutable
would be nice, very similar to how libraries deal with@Nullable
. I wouldn’t have a boolean (or I’d have that behavior on by default). The likeliness of someone using a rogue@Immutable
that doesn’t mean what we think it means seems pretty low.