-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
An error will occur if you name your protobuf service "Result" #1156
Comments
Yeah, i think this is something that is hard to fix due to Result being imported in the prelude. I would consider changing the name as it may just be incompatible with Rust. |
I think if the generated code used a fully qualified path like |
Great idea, I think I can open up a PR in the weekend if we're going with this way |
Bug Report
Version
Platform
Description
I found out an unique bug, I happened to name my proto service as "Result" because it's supposed to stream the result of a service. Here is my proto definition:
result.proto
Then when I run
cargo build
where inside in the build.rs looks like:build.rs
It will show this error:
For me the fix was to rename the protobuf service in
result.proto
to another name.result.proto
I'm reporting this bug because it works just fine when I compile the protobuf with
protoc
for the Golang side.The text was updated successfully, but these errors were encountered: