[
https://issues.apache.org/jira/browse/THRIFT-455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13676933#comment-13676933
]
Carl Yeksigian commented on THRIFT-455:
---------------------------------------
A few thoughts to get the ball rolling on this again:
# We should not allow any field to have no specification as to what state it is
# We need three states to capture the current abilities
# We need to rename the current states so that they are not opposites of each
other
The three states are:
# required for serialization and deserialization ("required")
# optional for serialization and deserialization ("optional")
# required for serialization, optional for deserialization (not specified)
Now the hard part is coming up with 3 names that describe the states.
> Compiler flag to make optional/required field modifiers compulsory
> ------------------------------------------------------------------
>
> Key: THRIFT-455
> URL: https://issues.apache.org/jira/browse/THRIFT-455
> Project: Thrift
> Issue Type: New Feature
> Components: Compiler (General)
> Reporter: Bryan Duxbury
>
> if we are unwilling to globally require users specify "required" or
> "optional" when creating their structs, I think we should at least add a
> command line switch that causes us to enforce that behavior. It would
> certainly make my implementations more reliable, especially when I'm giving
> non-experts the tools to make their own IDLs.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
