[
https://issues.apache.org/jira/browse/THRIFT-455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12743231#action_12743231
]
Jonathan Ellis commented on THRIFT-455:
---------------------------------------
> fields are assumed present in C++, but not required when reading
I have no idea what this means, but having fields that are neither required nor
optional and get special cased differently in different places of the code is
broken.
If you really want to have 3 states then 2 of them should not be called
"required" and "optional" because common sense implies that if a field is not
one it must be the other.
> 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.
-
You can reply to this email to add a comment to the issue online.
