Creating a list without duplicates from other list.
CvRXX opened this issue · 6 comments
CvRXX commented
Hello,
I'm wondering how I could do the following with brigand:
We have a list A which contains types which have subtypes:
using A = brigand::list<T1<ST1>,T2<ST1>,T3<ST2>,T4<S2>,T5<ST3>>
for example T1 looks like this:
template<SubType>
struct T1{
using ST = SubType;
}
I would like to make from this list a list of subtypes without duplicates. So it would look like this:
brigand::list<ST1, ST2, ST3>
How do I achieve such a thing with brigand. Thanks in advantage!
BTW: This is an epic library, keep up the good work!
edouarda commented
Would creating a set solve your problem?
CvRXX commented
But how do I get the sub types from the other list in?
edouarda commented
You write a functor with a copy algorithm?
CvRXX commented
oke, will try that
CvRXX commented
Ah oké, but how do I get the sub types in there then?
…On 22 December 2016 10:38:39 CET, "Edouard A." ***@***.***> wrote:
Would creating a set solve your problem?
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
#226 (comment)
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
odinthenerd commented
The way join is implemented it should unwrap the types for you
…----- Ursprüngliche Nachricht -----
Von: "Carlos van Rooijen" <notifications@github.com>
Gesendet: 22.12.2016 21:01
An: "edouarda/brigand" <brigand@noreply.github.com>
Cc: "Subscribed" <subscribed@noreply.github.com>
Betreff: Re: [edouarda/brigand] Creating a list without duplicates from otherlist. (#226)
Ah oké, but how do I get the sub types in there then?
On 22 December 2016 10:38:39 CET, "Edouard A." ***@***.***> wrote:
Would creating a set solve your problem?
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
#226 (comment)
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.