why wouldn't you recommend it (i haven't read what...

# announcements

[tipsy]

why wouldn't you recommend it (i haven't read what it does yet)

[kingsley]

It basically marks those methods as synthetic in the byte code, which has a different use case altogether. Checkout https://www.javaworld.com/article/2073578/java-s-synthetic-methods.html
Making them hidden from Java is just one of it’s side effects

[tipsy]

yeah, trying to read about it

[tipsy]

but i don't understand how that can have any downsides yet

[kingsley]

I don’t think there’s any particular downside to it. I guess it’s just using the wrong tool to solve a problem

[tipsy]

what would the right tool be?

[kingsley]

Haha. If I knew, we would be having a different kind of conversation 😄

[tipsy]

i feel like if they always made getters/setters synthetic for internal properties, it would behave a lot more like the name implies

[kingsley]

But that would also make the getter/setters invisible from Java, even in the same module

[tipsy]

i feel like that's better than exposing it as

get<property>$production_sources_for_module_<module>
set<property>$production_sources_for_module_<module>

[tipsy]

that doesn't look like something you're supposed to use

[kingsley]

that doesn’t look like something you’re supposed to use

Exactly ☝️

[tipsy]

but that's how it looks from the same module in java..?

[tipsy]

if you use internal

[kingsley]

Yep.
Only difference is that IDEA highlights it as error from a different module

[tipsy]

yeah, no.. this doesn't make sense to me

[tipsy]

i think they should be invisible to java, even in the same module

[tipsy]

but i'll use your hack for now, thanks 😬