[dune-functions] performance impact of std::bind
Steffen Müthing
steffen.muething at iwr.uni-heidelberg.de
Sun Sep 27 12:16:18 CEST 2015
> Am 26.09.2015 um 21:40 schrieb Christian Engwer <christian.engwer at uni-muenster.de>:
>
> Dear fellow dune-functions fans :-)
>
> While trying to push our functions interfaces to the extrem I was
> wandering, what the performance impact of std::bind is.
>
> Does anybody have some insights?
I don’t have any hard measurements, but I would think that it’s negligible as long as the
curried parameters don’t have to be copied into the bind functor in an expensive fashion.
Slightly off-topic: I read somewhere that some parts of the committee consider std::bind mostly
obsolete with the advent of generic lambdas…
Steffen
>
> Ciao
> Christian
>
> _______________________________________________
> dune-functions mailing list
> dune-functions at dune-project.org
> http://lists.dune-project.org/mailman/listinfo/dune-functions
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 455 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <https://lists.dune-project.org/pipermail/dune-functions/attachments/20150927/b1d538db/attachment.sig>
More information about the dune-functions
mailing list