diff options
| author | Benoit Daloze <eregontp@gmail.com> | 2021-06-02 14:34:07 +0200 |
|---|---|---|
| committer | Benoit Daloze <eregontp@gmail.com> | 2021-06-02 14:34:07 +0200 |
| commit | 22e2a6a999b958efe5d84d9c7314e450fda82254 (patch) | |
| tree | b2dc946cf2fe2c250d0583675e548c67dca3e71a /spec/ruby/core/objectspace/define_finalizer_spec.rb | |
| parent | a4fbc7e2884ba694278adea3b32ddb8c2ac10efe (diff) | |
Update to ruby/spec@a0b7d0d
Diffstat (limited to 'spec/ruby/core/objectspace/define_finalizer_spec.rb')
| -rw-r--r-- | spec/ruby/core/objectspace/define_finalizer_spec.rb | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/spec/ruby/core/objectspace/define_finalizer_spec.rb b/spec/ruby/core/objectspace/define_finalizer_spec.rb index ed021b7131..281785b0a4 100644 --- a/spec/ruby/core/objectspace/define_finalizer_spec.rb +++ b/spec/ruby/core/objectspace/define_finalizer_spec.rb @@ -4,7 +4,7 @@ require_relative 'fixtures/classes' # Why do we not test that finalizers are run by the GC? The documentation # says that finalizers are never guaranteed to be run, so we can't # spec that they are. On some implementations of Ruby the finalizers may -# run asyncronously, meaning that we can't predict when they'll run, +# run asynchronously, meaning that we can't predict when they'll run, # even if they were guaranteed to do so. Even on MRI finalizers can be # very unpredictable, due to conservative stack scanning and references # left in unused memory. |