Aniket21mathur/Chapel-protobuf

Issues

• Task checklist (Features/TODO)

  #3 opened 4 years ago by Aniket21mathur
  7

• Do we explicitly need to have default values for message fields?

  #9 opened 4 years ago by Aniket21mathur
  6

• Rename modules and functions

  #12 opened 4 years ago by Aniket21mathur
  0

• Reflection support

  #28 opened 4 years ago by Aniket21mathur
  4

• Any support for Chapel

  #31 opened 4 years ago by Aniket21mathur
  4

• Review of protobuf user-end APIs

  #27 opened 4 years ago by Aniket21mathur
  12

• Avoid serialization of default values of scalar types to the wire

  #26 opened 4 years ago by Aniket21mathur
  0

• Write explanatory comments in the generated file

  #25 opened 4 years ago by Aniket21mathur
  0

• Remove explicit declarartion of `proc a` and `proc ref a ref` in generated chapel file

  #19 opened 4 years ago by Aniket21mathur
  0

• Remove extra imports

  #18 opened 4 years ago by Aniket21mathur
  0

• Make base append functions return length

  #17 opened 4 years ago by Aniket21mathur
  0

• Remove Mason support (files)?

  #7 opened 4 years ago by Aniket21mathur
  1

• Specifiy Chapel unique types via protocol buffer files?

  #4 opened 4 years ago by Aniket21mathur
  4

• Make access to wiretypes more generic in Message class

  #1 opened 4 years ago by Aniket21mathur
  0