Forums before death by AOL, social media and spammers... "We can't have nice things"
|    comp.lang.c++.moderated    |    Moderated discussion of C++ superhackery    |    33,346 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 31,750 of 33,346    |
|    Pete Becker to Stuart Heinrich    |
|    Re: Keyword "innate" to allow compile ti    |
|    19 Dec 11 23:48:17    |
      9d219648       From: pete@versatilecoding.com              On 2011-12-19 20:17:22 +0000, Stuart Heinrich said:              > There is no reason why the output of a simple function like "sin(1.5)"       > that has no side effects cannot be precomputed during compilation --       > no reason, except that the compiler may not be able to detect the fact       > that this function has no side effects.       >       > I propose a simple keyword "innate" to resolve this issue. If a       > function is declared with keyword innate, and the function is called       > using inputs that are all compile time constants, then the output of       > the function should be guaranteed to be a compile time constant as       > well.       >              How does this differ from the C++11 "constexpr"? |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca