AutoValue support

[adauvalter]

Any plans to support it?

[greenrobot]

Let's discuss how to do this. So, to actually update an object, you would have to create a new AutoValue object, I suppose?

[autovalue]

Yes, this feature would very much be appreciated! Most of my objects currently using AutoValue. And this would be a godsend!

[adauvalter]

To update an object either create a new one or use with extension. But I think that then we lose a main idea of Autovalue

[bnvinay92]

This is the only issue stopping us from adopting ObjectBox.

[greenrobot]

@bnvinay92 It seems like AutoValue is loosing ground against Kotlin offering data classes et al. What's your reason to sticking to it?

[bnvinay92]

We're a huge organisation that cannot migrate to Kotlin in the foreseeable future.

[greenrobot]

Fair enough. :) Cannot promise anything at the moment as we have our next releases planned, but would you be able to help a bit on that?

[bnvinay92]

Sure. How can I help?

[greenrobot]

Do you think we could expect that everyone implements a create method? (Builder would hit performance more.)

How do relation affect AutoValue objects? Can this be generalized in a meaningful way?