[dune-functions] TypeTree now works with dune-functions again

Oliver Sander oliver.sander at tu-dresden.de
Tue Sep 15 21:16:52 CEST 2015


> No, we can't fix index_sequence in dune-common, because this
> requires C++11, namely template aliases. The standard says,
> that index_sequence<i> _is_ an interger_sequence<size_t,i>,
> not derived, convertible, or anything else. But this can't
> be achieved without template aliases.
Yes, but we have template aliases in dune-common post-2.4, right?
--
Oliver

>
>>> The pre-made index objects now live in Dune::TypeTree::Indices (I thought the „Static“ was a little redundant).
>>> I really like the idea of those constants and would like to see them in dune-common after the release of 2.4.
>> Seconded -- then I could use them for MultiTypeBlockVector.
>>
>> Nitpicking: wouldn't constant_index be a better name than index_constant?
>> (I won't even try to enforce 'standard Dune' camelCase with you :-) )
> My proposal 'index_constant' tried to stay in line with index_sequence
> that also specializes some static index thingy for size_t. But t´since
> it's not in the standard using IntergerConstant would also be fine.
>
> Carsten
>
>
>
>
> _______________________________________________
> dune-functions mailing list
> dune-functions at dune-project.org
> http://lists.dune-project.org/mailman/listinfo/dune-functions

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.dune-project.org/pipermail/dune-functions/attachments/20150915/67a7b61d/attachment.htm>


More information about the dune-functions mailing list