You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@thrift.apache.org by "Jens Geyer (Jira)" <ji...@apache.org> on 2022/09/14 06:50:00 UTC
[jira] [Resolved] (THRIFT-5627) More consistent syntax for cpp_type
[ https://issues.apache.org/jira/browse/THRIFT-5627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jens Geyer resolved THRIFT-5627.
--------------------------------
Fix Version/s: 0.18.0
Resolution: Fixed
> More consistent syntax for cpp_type
> -----------------------------------
>
> Key: THRIFT-5627
> URL: https://issues.apache.org/jira/browse/THRIFT-5627
> Project: Thrift
> Issue Type: Improvement
> Components: Compiler (General)
> Reporter: Jens Geyer
> Assignee: Jens Geyer
> Priority: Major
> Fix For: 0.18.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> As a side effect on my current work I recognized an interesting parser warning.
> Essentially it boils down to the list<> case in these definitions taken from https://thrift.apache.org/docs/idl which (now) would cause ambiguities.
> {code}
> [28] MapType ::= 'map' CppType? '<' FieldType ',' FieldType '>'
> [29] SetType ::= 'set' CppType? '<' FieldType '>'
> [30] ListType ::= 'list' '<' FieldType '>' CppType?
> {code}
> I wonder why we need it this way at all. Wouldn't it be better if list<> set<> and map<> would expect the same syntax?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)