我知道未初始化的局部变量是未定义的行为(UB)，而且值可能有陷阱表示，这可能会影响进一步的操作，但有时我想使用随机数仅为视觉表示，而不会在程序的其他部分进一步使用它们，例如，在视觉效果中设置随机颜色的东西，例如:
void updateEffect(){
for(int i=0;i<1000;i++){
int r;
int g;
int b;
star[i].setColor(r%255,g%255,b%255);
bool isVisible;
star[i].setVisible(isVisible);
}
}
比那么快吗
void updateEffect(){
for(int i=0;i<1000;i++){
star[i].setColor(rand()%255,rand()%255,rand()%255);
star[i].setVisible(rand()%2==0?true:false);
}
}
也比其他随机数生成器快吗?
There are certain situations in which uninitialized memory may be safely read using type "unsigned char*" [e.g. a buffer returned from malloc]. Code may read such memory without having to worry about the compiler throwing causality out the window, and there are times when it may be more efficient to have code be prepared for anything memory might contain than to ensure that uninitialized data won't be read (a commonplace example of this would be using memcpy on partially-initialized buffer rather than discretely copying all of the elements that contain meaningful data).
然而，即使在这种情况下，人们也应该始终假设，如果字节的任何组合特别烦人，那么读取它总是会产生字节的模式(如果某个模式在生产中是烦人的，但在开发中不是，那么这种模式直到代码进入生产中才会出现)。
Reading uninitialized memory might be useful as part of a random-generation strategy in an embedded system where one can be sure the memory has never been written with substantially-non-random content since the last time the system was powered on, and if the manufacturing process used for the memory causes its power-on state to vary in semi-random fashion. Code should work even if all devices always yield the same data, but in cases where e.g. a group of nodes each need to select arbitrary unique IDs as quickly as possible, having a "not very random" generator which gives half the nodes the same initial ID might be better than not having any initial source of randomness at all.
不，太糟糕了。
使用未初始化变量的行为在C和c++中都是未定义的，而且这样的方案不太可能具有理想的统计属性。
如果你想要一个“快速而肮脏”的随机数生成器，那么rand()是你最好的选择。在它的实现中，它所做的只是一个乘法、一个加法和一个模数。
我所知道的最快的生成器需要你使用uint32_t作为伪随机变量I的类型，并使用
I = 1664525 * I + 1013904223
生成连续的值。你可以选择任何你喜欢的I的初始值(称为种子)。显然你可以内联编码。无符号类型的标准保证包装充当模数。(数字常数是由杰出的科学程序员Donald Knuth精心挑选的。)
正如其他人所注意到的，这就是未定义行为(UB)。
实际上，它(可能)实际上(有点)管用。在x86[-64]架构上读取未初始化的寄存器确实会产生垃圾结果，而且可能不会做任何坏事(与例如Itanium相反，那里的寄存器可以被标记为无效，因此读取会传播NaN之类的错误)。
但这里存在两个主要问题:
It won't be particularly random. In this case, you're reading from the stack, so you'll get whatever was there previously. Which might be effectively random, completely structured, the password you entered ten minutes ago, or your grandmother's cookie recipe.
It's Bad (capital 'B') practice to let things like this creep into your code. Technically, the compiler could insert reformat_hdd(); every time you read an undefined variable. It won't, but you shouldn't do it anyway. Don't do unsafe things. The fewer exceptions you make, the safer you are from accidental mistakes all the time.
UB更紧迫的问题是它使整个程序的行为没有定义。现代编译器可以使用它来省略大量的代码，甚至可以回溯到过去。玩UB就像维多利亚时代的工程师拆除一个活跃的核反应堆。有无数的事情会出错，而且您可能连一半的基本原则或实现的技术都不知道。这可能没什么，但你仍然不应该让它发生。看看其他漂亮的答案来了解细节。
还有，我会炒了你。
