[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: RFC: api.value.automove
|
From: |
Hans Åberg |
|
Subject: |
Re: RFC: api.value.automove |
|
Date: |
Wed, 19 Sep 2018 22:21:01 +0200 |
> On 19 Sep 2018, at 08:56, Akim Demaille <address@hidden> wrote:
>
> - should we not use YY_MOVE and just use std::move instead? In which
> case the parser _must_ be compiled in C++11+.
LilyPond uses a .yy file and has not yet migrated to C+++11, I think, though
they are working on it.
- RFC: api.value.automove, Akim Demaille, 2018/09/19
- Re: RFC: api.value.automove,
Hans Åberg <=
- Re: RFC: api.value.automove, Frank Heckenbach, 2018/09/20
- Re: RFC: api.value.automove, Akim Demaille, 2018/09/21
- Re: RFC: api.value.automove, Frank Heckenbach, 2018/09/21
- [PATCH 0/5] lalr1.cc: automove, Akim Demaille, 2018/09/22
- [PATCH 1/5] tests: prepare a test for automove, Akim Demaille, 2018/09/22
- [PATCH 2/5] tests: c++: use a custom string type, Akim Demaille, 2018/09/22
- [PATCH 3/5] c++: introduce api.value.automove, Akim Demaille, 2018/09/22
- [PATCH 4/5] c++: issue a warning with a value is moved several times, Akim Demaille, 2018/09/22
- [PATCH 5/5] news: c++: move semantics, Akim Demaille, 2018/09/22