diff options
| author | Oskari Timperi <oskari.timperi@iki.fi> | 2018-04-04 23:31:36 +0300 |
|---|---|---|
| committer | Oskari Timperi <oskari.timperi@iki.fi> | 2018-04-04 23:31:36 +0300 |
| commit | 8b8a4a1432ae2d1c8f8b533610df35c707389609 (patch) | |
| tree | 044e20247f30e073b4dd2ee5c4ff6a4200cf5cb2 | |
| parent | bcc4e4539c31d47d6662a321c639e4c983261aeb (diff) | |
| download | nimpb-8b8a4a1432ae2d1c8f8b533610df35c707389609.tar.gz nimpb-8b8a4a1432ae2d1c8f8b533610df35c707389609.zip | |
Add TODO to not lose it :-)
| -rw-r--r-- | TODO | 25 |
1 files changed, 25 insertions, 0 deletions
@@ -0,0 +1,25 @@ +# The list of possible future improvements and ideas + +- Should we get rid of ProtobufStream and just use Stream? Can our write/read + procs interfere with other versions or should we prefix them with something? + Or should we make ProtobufStream a distinct Stream? Or does this matter at + all? + +- Make field names camelCase. This would make the generated code look more + Nim-ish, even though we can use most of the symbols in whatever way we want + as Nim ignores most underscores and case. + +- Preserve unknown fields on deserialize/serialize. This has been implemented + for protobuf 3.5.0 for proto3. I think it's a nice thing. + +- Proto2 extensions? This needs some thinking how to do this. How often are + extensions used? Is this necessary? + +- Options? + +- has/clear procs for oneofs to check/clear the whole oneof. Has is simple. + What about clearing, we are storing the fields in an object tagged with + {.union.} pragma. How does Nim behave when one field of a union is reset + (was thinking about reference types and GC)? + +- JSON mapping for proto3? |
