-
```
It would be extremely useful to have some hooks so that some custom
functionality could be added. For example, hooks provided at following
places could be powerful and open up many new use cases…
-
# Proposal
I'd like to hear if there are any opinions on moving to a generated getter/setter API for fields in messages, enums etc. rather than simply making fields public and accessing them directly…
-
```
It would be extremely useful to have some hooks so that some custom
functionality could be added. For example, hooks provided at following
places could be powerful and open up many new use cases…
-
```
It would be extremely useful to have some hooks so that some custom
functionality could be added. For example, hooks provided at following
places could be powerful and open up many new use cases…
-
```
It would be extremely useful to have some hooks so that some custom
functionality could be added. For example, hooks provided at following
places could be powerful and open up many new use cases…
-
```
It would be extremely useful to have some hooks so that some custom
functionality could be added. For example, hooks provided at following
places could be powerful and open up many new use cases…
-
Rust already has a preferred naming style.
With #855:
+ the preferred formatting is default rustfmt
+ there is a preferred import order (f1b3732d90b15add5e03d046bcb3084047d3b586)
+ there is a m…
-
```
It would be extremely useful to have some hooks so that some custom
functionality could be added. For example, hooks provided at following
places could be powerful and open up many new use cases…
-
```
It would be extremely useful to have some hooks so that some custom
functionality could be added. For example, hooks provided at following
places could be powerful and open up many new use cases…
-
```
It would be extremely useful to have some hooks so that some custom
functionality could be added. For example, hooks provided at following
places could be powerful and open up many new use cases…