> On Wednesday, October 19, 2011 2:49:17 PM UTC-7, Dormando wrote: > > That startup option should flog you a dozen times first, and force you > to > agree that you're doing something very very wrong, but it should work. > The > default will forever stay at 250 bytes because it's a good idea, and > increasing the limit may seriously inflate the internal item structure > due > to alignment issues, at minimum one byte per item. > > > But what if I have > morethan 7458340731200206743290965315462933837376471534600406894271518333206278385070118304936174890400427803361511603255836101453412728095225302660486 > 164829592084691481260792318781377495204074266435262941446554365063914765414217260588507120031686823003222742297563699265350215337206058336516628646 > 003612927433551846968657326499008153319891789578832685947418212890625000000000000000000000000000000000000000000000000000000000000000000000000000000 > 000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 > 0000000000000000000000000000000 items I need to store? How will I address > them? > > (this is in the FAQ, isn't it?)
This reminds me of the old CAS patch. Where I removed the early wrap detector due to the fact that the sun would have engulfed earth before the wrap could plausibly occur (without the instance being restarted). All joking aside; while I am annoyed that I'll likely be the person who implements it, and it will do nothing but cause harm to people, it's a little silly to avoid allowing it entirely. -Dormando
