You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the capnp docs they mention a pattern where an annotation and the struct for its value share the same name.
structGrault {
value @0:Int32 = 123;
}
annotation grault(file) :Grault;
Because both annations and structs get corresponding rust modules the generated code won't build.
I'm not sure what the right solution is here. A robust but maybe annoying option would be to add a prefix to annotation modules so you get something like annotation_grault and grault. Just naming the struct GraultOpts isn't a big deal either.
The text was updated successfully, but these errors were encountered:
In the capnp docs they mention a pattern where an annotation and the struct for its value share the same name.
Because both annations and structs get corresponding rust modules the generated code won't build.
I'm not sure what the right solution is here. A robust but maybe annoying option would be to add a prefix to annotation modules so you get something like
annotation_grault
andgrault
. Just naming the structGraultOpts
isn't a big deal either.The text was updated successfully, but these errors were encountered: