Hi Kenton. That works for me and I like it. Moreover, it will be possible to consistently apply to all nested classes.
I am likely to look at this in August. Thank you! Brano On Fri, Jul 8, 2016 at 7:21 AM, Kenton Varda <[email protected]> wrote: > Hi Brano, > > Sorry, I'm uncomfortable carrying out that change without more research / > experimentation. > > A change I would be more comfortable with is to declare T_Client as a > top-level class with T::Client then being an alias to T_Client. This is > what Protobuf does with nested types. This way you can then forward-declare > T_Client. > > Thoughts? > > -Kenton > > On Thu, Jul 7, 2016 at 2:29 AM, Branislav Katreniak <[email protected]> > wrote: > >> Hi Kenton >> >> I would like to forward declare capnp generated client class. AFAIK this >> is not possible because it is generated as inner class. But this part of >> your earlier post would solve my problem: >> >> > * Capabilities: T::Client (I wonder if we should move T::Client's >> members into T and make T::Client be an alias for backwards-compatibility?) >> >> Are you willing to review & merge this change if I implement it? >> >> Kind regards >> Brano >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Cap'n Proto" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> Visit this group at https://groups.google.com/group/capnproto. >> > > -- > You received this message because you are subscribed to the Google Groups > "Cap'n Proto" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > Visit this group at https://groups.google.com/group/capnproto. > -- You received this message because you are subscribed to the Google Groups "Cap'n Proto" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. Visit this group at https://groups.google.com/group/capnproto.
