> Le 28 sept. 2018 à 12:35, Hans Åberg <[email protected]> a écrit :
>
>
>> On 28 Sep 2018, at 12:11, Akim Demaille <[email protected]> wrote:
>>
>>> Le 28 sept. 2018 à 10:35, Hans Åberg <[email protected]> a écrit :
>>>
>>>> On 28 Sep 2018, at 07:06, Akim Demaille <[email protected]> wrote:
>>>>
>>>> Do you think it’s useful? We used to use deques in the generated
>>>> parser, but in
>>>> http://lists.gnu.org/archive/html/bison-patches/2013-01/msg00010.html
>>>> we moved to vector because I don’t see what it buys us. Sure, it
>>>> saves us from occasional copies when the vector grows, but that’s
>>>> all. At the cost of more indirections.
>>>
>>> For types that can't be copied or moved, or does not have move, the deque
>>> might be desirable. Don’t know about that in this context, but a search
>>> shows that such things are out there.
>>
>> I know, that’s why we chose deques initially.
>
> Wasn’t there std::vector in the beginning of the millennium?
What is your question? Sure, C++ had deque and vector at the
same time. And Bison started with deque, and we moved to vector,
in 2013:
>>>> http://lists.gnu.org/archive/html/bison-patches/2013-01/msg00010.html
