4 ms·
That's surprising, is there a technical reason? I would have guessed that a non-aliasing declaration was table stakes for any performance critical language, so
by dodobirdlord 7y ago
That's surprising, is there a technical reason? I would have guessed that a non-aliasing declaration was table stakes for any performance critical language, so I just always assumed it was in there somewhere.
- toolslive 7y agowith C++, you often wonder why some things are done in such an ugly way (or haven't been cleaned up). The standard reply is frequently "backward compatibility". But if you investigate the backward compatibility, you find C++ is not really backward compatible with C at all. FWIW 'restrict' was introduced in C99, so after the big rift. But you can use '__restrict'