Jordan Zimmerman
Jordan Zimmerman
I now believe this is a JDK/Java limitation. Look at this quote from: https://docs.oracle.com/en/java/javase/25/language/compact-source-files-and-instance-main-methods.html#GUID-E49690F1-727E-45F6-A582-9821C9597112 > The code of a compact source file can't refer to its implicitly declared class by...
Annoyingly, there's no reliable way to tell that you're in a compact source file during annotation processing so there's no way for RecordBuilder to log an error.
I'd need to see an example. If it implements an interface there would have to be an implementation for the methods.
The generated `With` interface has this. I still don't understand the benefit here.
`@RecordInterface` has been a problem for a while. There seem to be bugs in the various Java compilers/build tools. I _may_ have a workaround. I'll try to get to it...
I was working on something similar with this: https://github.com/Randgalt/record-builder/discussions/120 - but that was way more experimental.
I'm open to PRs on this.
@pawellabaj could you provide a PR?
> Do you consider introducing Guava as a dependency to your project No - we shouldn't do that. We could, however, do FQPN string comparisons if needed.
At this point I'd like to limit any new customizations. This library ran into a lot of problems with some of the recently added customizations.