Re: RFC: c++: provide control over the stack.hh file name

[Hans Åberg]

> On 28 Sep 2018, at 12:11, Akim Demaille <address@hidden> wrote:
> 
>> Le 28 sept. 2018 à 10:35, Hans Åberg <address@hidden> a écrit :
>> 
>>> On 28 Sep 2018, at 07:06, Akim Demaille <address@hidden> 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?

> But in reality, given
> that we have to copy (or move) to/from the stack to the actions, I’m
> not sure this constraint really makes sense.

You can skip it, as for me.