Age | Commit message (Collapse) | Author |
|
|
|
RDoc cannot know if bare words are method name or not.
|
|
This may be too verbose, if so, maybe it should be moved lower in
the document, or to a separate document.
|
|
a frozen String
* Always the same frozen String for each of these values.
* Avoids extra allocations whenever calling these 3 methods.
* See [Feature #16150]
Notes:
Merged: https://github.com/ruby/ruby/pull/2492
|
|
C API updates:
* adjusted indent.
* marked up ANYARGS as RDoc.
|
|
* got rid of inadvertent label lists.
* marked up resolve_feature_path method names.
* fixed indentation of UnboundMethod#bind_call and marked up as
RDoc.
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/2488
|
|
|
|
* Always the same frozen String for a given Module or Class.
* Avoids extra allocations whenever calling Module#name.
* See [Feature #16150]
Notes:
Merged: https://github.com/ruby/ruby/pull/2487
|
|
* Always the same frozen String for a given Symbol.
* Avoids extra allocations whenever calling Symbol#to_s.
* See [Feature #16150]
Notes:
Merged: https://github.com/ruby/ruby/pull/2437
|
|
[Feature #11297] [Feature #16123]
|
|
|
|
|
|
|
|
|
|
|
|
[Feature #11297] [Feature #16123]
|
|
|
|
|
|
|
|
|
|
Notes:
Merged-By: nobu <nobu@ruby-lang.org>
|
|
Patch by darkphnx (Dan Wentworth) . Thanks!
[Feature #15964]
|
|
|
|
Since 50f5a0a8d6e7ad89d6caff695a08dbd38edb7a6e, some C++ extensions
needed fixes like https://github.com/eagletmt/faml/pull/49 to make their
build succeed.
Thus it's worth noting that C API declarations are changed.
|
|
A follow up for 16c6984bb9..b5b3afadfa. [Feature #14183]
|
|
Related to [Feature #15955].
|
|
`umethod.bind_call(obj, ...)` is semantically equivalent to
`umethod.bind(obj).call(...)`. This idiom is used in some libraries to
call a method that is overridden. The added method does the same
without allocation of intermediate Method object. [Feature #15955]
```
class Foo
def add_1(x)
x + 1
end
end
class Bar < Foo
def add_1(x) # override
x + 2
end
end
obj = Bar.new
p obj.add_1(1) #=> 3
p Foo.instance_method(:add_1).bind(obj).call(1) #=> 2
p Foo.instance_method(:add_1).bind_call(obj, 1) #=> 2
```
|
|
|
|
This reverts commits:
* d365fd5a024254d7c105a62a015a7ea29ccf3e5d
* d780c3662484d6072b3a6945b840049de72c2096
* aa7211836b769231a2a8ef6b6ec2fd0ec882ef29
* 043f010c28e82ea38978bf8ed885416f133b5b75
* bb4dd7c6af05c7821d572e2592ea3d0cc748d81f
* 043f010c28e82ea38978bf8ed885416f133b5b75
* f169043d81524b5b529f2c1e9c35437ba5bc3a7a
http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-core/94645
|
|
pushing a trivial commit for testing post-receive hook
|
|
|
|
|
|
|
|
|
|
Thanks for the patch gareth (Gareth Adams). [Bug #15933]
-------
Combines two small, but very related changes
1: Treat HTTPS the same as HTTP
Previously, OpenURI followed guidance in RFC2616/3.7.1:
> When no explicit charset parameter is provided by the sender, media
> subtypes of the "text" type are defined to have a default charset
> value of "ISO-8859-1" when received via HTTP.
However this RFC was written before TLS was established and OpenURI was
never updated to treat HTTPS traffic the same way. So, HTTPS documents
received a different default to HTTP documents.
This commit removes the scheme check so that all text/* documents
processed by OpenURI are treated the same way.
In theory this processing gets applied to FTP URIs too, but there's no
mechanism in OpenURI for FTP documents to have Content-Type metadata
appended to them, so this ends up being a no-op.
2: Change default charset for text/* to UTF-8
Replaces the default ISO-8859-1 charset previously defined in RFC2616 (now
obsoleted) with a UTF-8 charset as defined in RFC6838.
Fixes: https://bugs.ruby-lang.org/issues/15933
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
- Add note regarding IA64 removal.
- Add note about Thread allocation performance improvements.
|
|
[Feature #10771]
|
|
[Feature #15777]
Closes: https://github.com/ruby/ruby/pull/2173
|
|
|
|
|