Hi folks, Some time ago (in GROOVY-11516) I started trying to find a path to go down that would reduce some inconsistencies I saw in how we were handling "internal" properties, including different behaviors at runtime and compile time.
I was looking for the quick fix for the problem I was working on at the time. The proposal didn't feel right so it was never progressed, and I eventually closed it. More recently, I started thinking about the problem again, and I think I have a path forward. I thought I would capture this in a GEP: https://groovy.apache.org/wiki/GEP-17.html There is also a related PR and Jira issue. Currently the GEP is part stating our design, and part an implementation plan for moving the relevant parts towards that design. My thinking was keep everything in the one spot for now, and once we're finished, just leave the "design statement" part behind. I think that captures our design decisions slightly better than just the code. It makes it easier for folks integrating into Groovy to know what to do and, these days I guess, easier for bots to learn how to best code for Groovy. Anyway, feedback welcome. Cheers, Paul.
