IssueTracker

since these are in public API (:/) we need to do this in 1.2

Opening diff shortly

Project: platform/frameworks/support
Branch: androidx-master-dev

commit d576cbdc911cba16638a44fd8223391a90a07ef7
Author: Mike Nakhimovich <digitalbuddha@users.noreply.github.com>
Date:   Tue Aug 11 09:30:34 2020

    [GH] Hide deprecated internal API.
   
    ## Proposed Changes
   
    * `RoomDatabase.java` has protected `mCallbacks` field which is leaking in the API docs, we should @Hide it.
   
    ## Testing
   
    Test: Ran unit tests locally
   
    ## Issues Fixed
   
    Fixes: 76109329
   
    This is an imported pull request from https://github.com/androidx/androidx/pull/61.
   
    Resolves #61
    Github-Pr-Head-Sha: 6440daa3a63752c7f9d5ba2a390248cd85bc634f
    GitOrigin-RevId: fe92d8466a59b44b218b6ca3cbd57dcda17992f7
   
    Change-Id: Id599cdf5b02b32bdae0166266fb7da967598fe92

A       room/runtime/api/current.ignore
M       room/runtime/api/current.txt
M       room/runtime/api/public_plus_experimental_current.txt
M       room/runtime/api/restricted_current.txt
M       room/runtime/src/main/java/androidx/room/RoomDatabase.java

https://android-review.googlesource.com/1396827

so turns out this is not about kotlin.

does not work w/ javac either because parameter names are not part of the class signature unless compiled w/ debug.

We will need to add a new annotation to support this.

True on the javac bit, but for kotlin you should be able to read the parameter names from the `@Metadata` annotations (since the param names are part of the public API in kotlin). There's no public API around this today though admittedly :/

actually i have a CL that makes this work for java as well but may not work for release builds (didn't try)

but it is shady, uses private APi and someday will break.

on the other hand, kotlin version seems to make sense, I'll ask kotlin folks to see if they have any plans to open it up.

we've added support for kotlin using kotlin-metadata. will go out in 1.1 alpha 2

I don't think this is really fixed. Room will still always pick the no-arg constructor rather than the primary constructor if one is found, which means you can't use immutable `val` dependencies. Taken up in https://issuetracker.google.com/issues/105769985 though

Or more specifically, you can't have nullable val properties (not dependencies, misspoke earlier). If I have a class with all val properties, it works fine