Code Monkey home page Code Monkey logo

dr_strangetemplate's People

Contributors

jamesqo avatar mcgallaspy avatar

Stargazers

avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar

Watchers

avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar

Forkers

claudiouzelac artisdom dxq-git alamantia kpotash shanfl scw000000 stoeckley hanumathrao siwenzhang aadebuger ring2003 gomson paulls20 lizida fbunn preejackie wxywb boradeanup goldstar111 anematode jarlene gurpreetshanky raf8 jiaoshihao chekaru juampatronics saswata-dutta qianqian121 jappoz angelo-abel dennymarx feng86 rtviii existedinnettw

dr_strangetemplate's Issues

count implementation is inefficient

Your implementation of count is quite inefficient and neddlessly increases compile times. This would be better:

template <class... T>
using count = std::integral_constant<std::size_t, sizeof...(T)>;

(as remarked on Hacker News by shin_lao: https://news.ycombinator.com/item?id=12575366)

Additionally, you use typedef a lot in the first example - I think using should be preferred, as it's easier to read (and can be templated).

First example no good?

The internet at large has suggested that the first example doesn't really improve using a C API. While I don't think those criticisms are without merit, I've decided to keep it up for now because it serves my main goal of introducing concepts like SFINAE.

As for whether it is actually a detriment to wrap a C-style API in the way I've suggested, in my opinion it's neither clearly a detriment nor a great improvement. The argument seems to be that it makes the code needlessly more complex. I consider that a matter of opinion.

But please feel free to comment here if you feel strongly about it!

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.