diff options
| author | normal <normal@b2dd03c8-39d4-4d8f-98ff-823fe69b080e> | 2017-07-12 18:31:07 +0000 |
|---|---|---|
| committer | normal <normal@b2dd03c8-39d4-4d8f-98ff-823fe69b080e> | 2017-07-12 18:31:07 +0000 |
| commit | d15cc7a6a33435bff59aeffb4721bed3bc7e43ed (patch) | |
| tree | 469067279d1db984fa573accb8c5e8b41cd02367 | |
| parent | 98f0a52845d0faff5aa9e44a3fb3de4d935f31e7 (diff) | |
doc/extension.rdoc: update wikipedia link to HTTPS
Avoid the latency for HTTP -> HTTPS redirect
* doc/extension.rdoc: update wikipedia link to HTTPS
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@59319 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
| -rw-r--r-- | doc/extension.rdoc | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/extension.rdoc b/doc/extension.rdoc index e89d4228e3..8a99f5d363 100644 --- a/doc/extension.rdoc +++ b/doc/extension.rdoc @@ -1721,7 +1721,7 @@ RGenGC (mostly) keeps compatibility. Generally, the use of the technique called write barriers is required in extension libraries for generational GC -(http://en.wikipedia.org/wiki/Garbage_collection_%28computer_science%29). +(https://en.wikipedia.org/wiki/Garbage_collection_%28computer_science%29). RGenGC works fine without write barriers in extension libraries. If your library adheres to the following tips, performance can |