Closed johndpope closed 7 years ago
i ended up resolving this by flattening out the protobuffer. perhaps some day - could use a protocol extension to simplify this. https://github.com/johndpope/tensorflow/blob/256ee4fb4b95c050275acc433005bc75b7e023a7/tensorflow/swift/Sources/GenerateOps.swift
https://github.com/SwiftGen/StencilSwiftKit/issues/50
I have confirmed this sample working fine.
For my case, I have some swift protobuffer classes that are auto generated by Apple.
here's the actual class https://github.com/johndpope/swift-grpc-tensorflow/blob/master/Sources/op_def.pb.swift
Basically it implements SwiftProtobuf.Message public struct Tensorflow_OpDef: SwiftProtobuf.Message (protocol only)
from what I can see - the only difference between the struct Article and struct Tensorflow_OpDef
is the getters / setters
when I reference the internal code / then it works.
Expected
doesn't render any results.
(I get that this may not be fixable. but maybe some warnings could be added to help debug.)