Just to be clear, the issue isn't when (or how often) the seed is set, it's when (AND how often) `srand` is called. I'm a little confused on how someone would create a gem that calls `srand` earlier, as I would expect RSpec to call it directly at some point after loading the gem or extension. What am I missing?

The documentation is great, but if you don't go reading every doc, you shouldn't be left scratching your head simply because you didn't take the time to do so - the principle of least surprise (which is prevalent in Ruby and the Ruby community).

This is the behavior that I would like to see supported:

```ruby
# spec/spec_helper.rb
srand 123

# spec/random_spec.rb
require 'spec_helper'

describe 'randomness' do
  it 'can be replicated' do
    5.times { print rand(99) }
  end
end
```

Where running `rspec spec/random_spec.rb` (note the lack of `--seed` in this call) would result in the same output every time. Do you see either (or both) of your suggestions supporting this behavior?

This seems like it is basic Ruby behavior that should not appear broken to users. I contend that it is better to 'break' gems/extensions in the RSpec ecosystem than it is to 'break' Ruby. And really, I'm still not entirely clear on how disabling access to setting the seed would break anything anyway. The seed should already only be set from the command line if it is being set at all (again, per RSpec's current documentation). I am only proposing that a (very good) suggestion be made a rule.