Activity
From 03/19/2019 to 03/25/2019
03/25/2019
-
10:50 PM Feature #14183: "Real" keyword argument
- Since I think it is best to back proposed behavior changes with a proposed implementation, attached is a patch based on mame's keyword-argument-separation branch that implements my proposal:
* Same behavior as mame's for methods that ... -
08:53 PM Feature #15438: Threads can't switch faster than TIME_QUANTUM_(NSEC|USEC|MSEC)
- sylvain.joyeux (Sylvain Joyeux) wrote:
> > Does it matter what the exact timeslice is in absolute units, or what matters is how often is a high-priority Thread executed compared to a low-priority Thread?
> ...
OK, then I think it would... -
12:32 PM Feature #15438: Threads can't switch faster than TIME_QUANTUM_(NSEC|USEC|MSEC)
- > Does it matter what the exact timeslice is in absolute units, or what matters is how often is a high-priority Thread executed compared to a low-priority Thread?
The actual underlying behavior matters, actually. If I'm using Linux sc... -
07:38 PM Misc #15723: Reconsider numbered parameters
- Great explanation, thanks :)
If it will be multiple params `@1`, `@2`, etc. Can we also have `@` aliasing `@1`? I think it's going to be a common use case to just have the one param. -
- maedi (Maedi Prichard) wrote:
> jeremyevans0, is it possible to have method/property calls that when without an object, reference the "current item" of the block they are in?
> ...
Think about handling:
```ruby
posts.each { puts .a... -
- jeremyevans0, is it possible to have method/property calls that when without an object, reference the "current item" of the block they are in?
```ruby
posts.each { .author = 'Santa Clause' }
```
This stops the range situation (`..`).... -
- pascalbetz (Pascal Betz) wrote:
> Aren't there any other symbols we can use? paragraph, backtick, caret, (double-)dagger, ...?
We should not add any sigils that are non-ASCII. That removes paragraph, dagger, double-dagger.
`^` (c... -
- Why not a single dot? (`.`) It mirrors the UNIX concept of "current directory":
```ruby
[1, 2, 3].each { puts . }
```
With a method/property:
```ruby
posts.each { ..author = 'Santa Clause' }
```
Keeps it simple. Makes it easier... -
04:48 PM Misc #15723: Reconsider numbered parameters
- > While I'm not totally against your opinion, I would like you to understand that this feature was not made out of thin air; it was feature requested. People think this is a neat feature. If you are against the feature itself not against...
-
12:37 PM Misc #15723: Reconsider numbered parameters
- @sawa Obsoleting and recycling `?` or ` sigils sounded like a nice idea at first, but incompatibility caused by the obsoletion remains years (or even decades). It seems nearly impossible.
Matz.
-
12:12 PM Misc #15723: Reconsider numbered parameters
- shyouhei (Shyouhei Urabe) wrote:
> pascalbetz (Pascal Betz) wrote:
> ...
I know that this feature was not made out of thin air. But out of a 8 year old request that does not show a real benefit (other than "it's a bit shorter").
The h... -
07:47 AM Misc #15723: Reconsider numbered parameters
- Here are some alternative sigils.
Provided that we obsolete the character literal notation `?a # => "a"`, which is rarely used, then we may use the `?` sigil like:
```ruby
[1, 2, 3].each { puts ?1}
```
Provided that we obsolet... -
- As the person who suggested the `@1` syntax, I guess I should give my opinion.
First, any approach that did not use a sigil (e.g. `this` or `it`) would probably break backwards compatibility, and that is not considered acceptable. ... -
- I think the usefulness of this feature is when there's only one parameter. When there's multiple parameters it becomes more confusing to read `@1`, `@2`, `@3` and less confusing to just name the variables.
I think limiting the "magic ... -
- I think there has been strong desire over the years for a shorthand feature like this, and it is unrealistic to ask for the feature to be withdrawn completely.
However, it is true that there is controversy regarding the use of the sig... -
01:33 AM Misc #15723: Reconsider numbered parameters
- pascalbetz (Pascal Betz) wrote:
> `{@1 * @2}` could easily be written as `{|a, b| a * b}` some chars more, yes. But IMHO more readable. I don't think that the language should be extended for something that does not have any benefit besi... -
02:26 PM Revision c92c0a59 (git): Prefer using vm_base_ptr rather than cfp->bp
- in MJIT implementation.
This allows us to drop cfp->bp by just modifying vm_base_ptr in the
future.
No performance impact:
$ benchmark-driver benchmark.yml --rbenv='before::before --disable-gems --jit;bp_::after --disable-gems --jit;v... - 06:58 AM Revision 7976d0d1 (git): * 2019-03-25
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67343 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
06:58 AM Revision 8dd0fb90 (git): use cfp->bp more.
- cfp->bp was (re-)introduced by Kokubun san, but VM doesn't use it
because I (ko1) want to remove it in a future. But using it make
leave instruction fast because of sp consisntency check.
So now VM uses cfp->bp.
To use cfp->bp, I checke... -
02:52 AM Feature #15626: Manual Compaction for MRI's GC (`GC.compact`)
- > I'll take a look at the core file, but can you give more info so I can try locally?
I just start my current project with passenger installed
I will create a sample project to reproduce this issue
Takes time though (stealing work t... -
01:54 AM Feature #15626: Manual Compaction for MRI's GC (`GC.compact`)
- @duerst: looks like he's updated his approach a bit since I last saw the talk (quite awhile ago!) But here's a 2017 version: https://www.youtube.com/watch?v=ptG5HtmvQx8
At around 19:45 he's talking about compacting before fork.
Whe... -
12:52 AM Feature #15667: Introduce malloc_trim(0) in full gc cycles
- @mame / @carlos, absolutely, I just need a few more days here, mounting this kind of test is not trivial even with docker containers.
03/24/2019
-
06:02 PM Bug #15726 (Closed): Error compiling Ruby
- Hello,
I'm sorry if I'm reporting that to the wrong place but the errors are so meaningless that it's hard to know where the issue really comes from.
Trying to install Ruby by compiling it, several errors happen. The process follow... -
- > I guess we could ... but on MRI we would still have to "guess" what are both the lowest and highest time slices we want to support forever and embed that in the value. Not really a very good prospect IMO.
Does it matter what the exa... -
- matz (Yukihiro Matsumoto) wrote:
>
> ...
A compromise does not sound like something that should be added to the language.
`{@1 * @2}` could easily be written as `{|a, b| a * b}` some chars more, yes. But IMHO more readable. I don... -
05:51 AM Misc #15459: DevelopersMeeting before/after RubyKaigi2019
- [Feature #15553] `Addrinfo.getaddrinfo` supports timeout
* I would like to have your opinion for patch2.diff -
- I updated the patch.
* get rid of Timeout from ext/socket/lib/socket.rb. If getaddrinfo_a() is not available, timeout is ignored. - 12:28 AM Revision 9f05891c (git): * 2019-03-24
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67341 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
12:28 AM Revision 831e93d9 (git): Update power_assert to 1.1.4
- This update fixes a failure of test-bundled-gems, so we revert r67275.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67340 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
03/23/2019
-
09:50 PM Feature #15626: Manual Compaction for MRI's GC (`GC.compact`)
- @naruse:
> I want to introduce this feature in Ruby 2.7.0-preview1.
> ...
Yes. I need to fix a bug with THEAP integration and I'll commit this along with NEWS.
@ko1:
> I'm not sure we can accept the "Known Issue". GC.verify_co... -
12:57 AM Feature #15626: Manual Compaction for MRI's GC (`GC.compact`)
- noahgibbs (Noah Gibbs) wrote:
> Aaron has commented on this in his talks -
Any pointers?
> ...
-
- BTW, MRuby 2.0.0 also copies the backtrace (because it implements Exception#exception as clone + setting the message):
```
$ mruby -e 'begin raise "foo"; rescue => e; c=e.exception "bar"; p c.backtrace; end'
["-e:1"]
```
... -
- OK ... since it seems that everyone is camping on their own position, I have an alternative proposal: initialize the min and max priority values using environment variables on MRI, defaults to -3 and 3. Would that be alright ?
-
02:03 PM Feature #15725: Proposal: Add Array#reverse_sort, #revert_sort!, #reverse_sort_by, and #reverse_sort_by!
- As this is a duplicate it may be best to discuss it in #12648.
I have not yet commented so just briefly; I am mostly neutral, can see
both ways. I think a slight problem is that the method names can be
a bit long and clumsy, especi... -
10:13 AM Feature #15725 (Rejected): Proposal: Add Array#reverse_sort, #revert_sort!, #reverse_sort_by, and #reverse_sort_by!
- Hello,
I would like to propose four new methods: `#reverse_sort`, `#revert_sort!`, `#reverse_sort_by`, and `#reverse_sort_by!` to Array.
These methods provides the most efficient way for user to get a reversed sorted array by calli... -
- Applied in changeset trunk|r67338.
----------
file.c: raise NotImplementedError instread of Errno::ENOSYS
[Misc #15615] - 10:41 AM Revision 7e421044 (git): * 2019-03-23
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67339 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- [Misc #15615]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67338 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
07:52 AM Bug #12667: full_gem_path is incorrect for core modules
- See https://github.com/bundler/bundler/issues/6930#issuecomment-475848401
-
- This patch was already applied.
-
01:10 AM Feature #14982: Improve namespace system in ruby to avoiding top-level names chaos
- I like this idea (and the other suggestions and implementations). I proposed something similar for Crystal a while back [here](https://github.com/crystal-lang/crystal/issues/4439).
03/22/2019
-
- @nobu and other MRI committers: what do you think?
It's somewhat inconsistent with Exception#clone which does copy the backtrace.
Would it make sense to follow JRuby and TruffleRuby's behavior, by copying the backtrace too, here? -
09:18 PM Feature #15724: Optionally suppress output from IRB for assignment expressions
- shevegen (Robert A. Heiler) wrote:
> I don't know if the original suggestion is good as is, but I think it is an interesting idea to support
> ...
The only option is `@context.echo` which turns all echo-ing on or off.
> I don't thin... -
- alanwu (Alan Wu) wrote:
> You can type `a = 1; nil` to stop irb from calling inspect on the assignment expression result, just FYI.
Yes, this feature is so that one doesn't have to remember to do that after each expression they would... -
- While I use a similar approach suggested by Alan Wu - and there is nothing wrong with that - I think
it may still be useful to have a simpler toggle-way for silencing output by default (or, via a toggle).
I don't know if the original... -
03:49 PM Feature #15724: Optionally suppress output from IRB for assignment expressions
- You can type `a = 1; nil` to stop irb from calling inspect on the assignment expression result, just FYI.
-
- Most REPLs I've used don't print out the output of assignment expressions like `a = 1`. Being able to suppress this output is very useful when you have a string which is essentially a blob, an object with a large string representation, ...
-
- One problem with automatically compacting on full GC: compaction appears to require two full GCs to do its thing. It might be possible to integrate this into Ruby's normal cycle. But I don't think this is designed for that as-is.
Aaro... -
- I got segfault with this patch
I added 1 extra change to fix compile error on MacOS
https://github.com/ruby/ruby/compare/trunk...PikachuEXE:feature/gc-compact/15626
Installed via
rvm install ruby-head --reconfigure --repo https://g... -
07:22 PM Misc #15723: Reconsider numbered parameters
- @matz wrote:
> I am not fully satisfied with the beauty of the code with numbered parameters, so I call it a compromise.
@shevegen wrote:
> ...
Sorry, but it sounds like the new feature is an ugly compromise ...
I learned Ruby – ... -
- alanwu (Alan Wu) wrote:
> The feature isn't even release[d] and we have confusion already #15708.
That is because it has not been documented yet. After the comments from the developers, now I understand it. There is no problem unders... -
- I don't like this feature because it adds a special case to the meaning of `@`.
Before this, I can look at `@` and understand that it's an instance variable, now there is extra mental overhead.
Every new feature added to the language... -
02:18 PM Misc #15723: Reconsider numbered parameters
- @sos4nt, I agree with you. Naming a parameter is good, I think.
By the way, The Ruby Style Guide that you mentioned says:
```
# bad
names.map { |name| name.upcase }
# good
names.map(&:upcase)
```
I dislike this style too... -
- I personally like the change. I think it is good for quick debugging.
Stefan picked only one example, though:
Hash.new { @1[@2] = "Go Fish: #{@2}" }
But who is to say that ruby users have to (only) write code like the above?... -
- Yes, I admit `{ @1[@2] = "Go Fish: #{@2}" }` is cryptic. But `{@1 * @2}` is not. So use numbered parameters with care (just like other features in Ruby). The **possibility** to make code cryptic itself should not be the reason to withdra...
-
- I just learned that *numbered parameters* have been merged into Ruby 2.7.0dev.
For readers not familiar with this feature: it allows you to reference block arguments solely by their *index*, e.g.
```ruby
[1, 2, 3].each { |i| puts ... -
05:36 PM Bug #15712: DateTime#=== should be defined and compare date and time instead of just the date
- @nobu Not sure why I wrote false (maybe I confused === with == in my testing), I'm getting `true` on ruby 2.5.3, 2.6.1, 2.6.2 and ruby-head (2.7.0 (same as the one registered in the issue)).
```
rvm ruby-head do ruby -e 'require "dat... -
- This is an interesting idea. I have not thought through all implications but not withholding
that, I like it so +1 from me. I think matz has to decide whether this may be useful. Since
I love `case`/`when` in ruby in general, any extens... -
- If such method, if any, should be rather defined on `Object`, that would be fine. I was not sure whether I should have requested this for `Kernel` or for `Object`.
-
- osyo (manga osyo) wrote:
> How about `Enumerable#case?` ?
> ...
What is to be evaluated is `bar`, not the objects that you put in the arrays. `bar` has to be the receiver. That also matches with how `case`-construction works. Furtherm... -
09:13 AM Feature #15722: `Kernel#case?`
- How about `Enumerable#case?` ?
Comparing with `===` like `Enumerable#include?`.
```ruby
bar # => "bar"
["foo", "bar", "baz"].case? bar # => true
["qux"].case? bar # => false
[Symbol, String].case? bar # => tru... -
- I often want to use `===` to match a single object on the right side against multiple objects on the left, as is used in `case`-constructions, just to return a truth value, and end up writing like this:
```ruby
bar # => "bar"
flag1 ... -
03:32 PM Misc #15610: Could bundler & rubygems be shipped in site_ruby?
- Just for completeness, this is my proposal:
https://bugs.ruby-lang.org/issues/5617 -
- svnpenn (Steven Penny) wrote:
> shevegen (Robert A. Heiler) wrote:
> ...
It's actually only 1 way. The `--` is just a command line option/argument parsing convention to mark an explicit break between options and arguments. It's useful ... -
- Since this ticket is closed, I've opened a new one to express my concerns:
https://bugs.ruby-lang.org/issues/15723 -
- gkemmey (Gray Kemmey) wrote:
> Is there a reason to do this other than to save some typing? I'm not sure we've proposed any terribly real-world cases here where this made code better.
Exactly my thought: Why? what will this make bett... -
- For those who want to change anything, I suggest to create new feature issues. It doesn't make sense to continue discussing a closed issue.
-
12:19 AM Feature #4475: default variable name for parameter
- As I'm reading through this I am warming up to this idea. However, I would prefer to keep `@` for instance variables.
Ruby currently does not allow naming variables or methods starting with a number. Could we utilize this?
```ruby... -
11:04 AM Revision 56557ec2 (git): [DOC] fix markups [ci skip]
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67337 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- I did update the latest patch: https://github.com/bundler/bundler/pull/7035
-
- Attached the patch for this feature.
-
- I might got a similar issue with 2.6.2 (also crash at os_log_type_enabled + 627)
https://bugs.ruby-lang.org/issues/15623#note-2
See update #2 -
- Add counters to count ccf (call cache fastpath) usage.
These counters will help which kind of method dispatch
is important to optimize.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67336 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- I came up with the method name:
```ruby
solid?
```
-
06:25 AM Feature #15721 (Open): optimize comparison of special const
- ## Description
optimize comparison between special consts in `comparable_by_identity`.
it is called from `==` .
## Benchmark
```ruby
num_array = Array.new(1_000_000) { 1 }
num_array.include? nil
# 0.156 => 0.0089 ... -
- 2.0.0 リリース時のディスカッションなので閉じておきます。
- 12:21 AM Revision 4d2bac1f (git): * 2019-03-22
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67335 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
- 12:21 AM Revision a433f2c5 (git): * expand tabs.
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67334 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- similar idea to r67315, provide the following optimization
for method dispatch with lead and kw parameters.
(1) add a special branch to check passing kw arguments to
a method which has lead and kw parameters.
ex) def foo(x, k:1)...
03/21/2019
-
11:33 PM Bug #15718: YAML raises error when dumping strings with UTF32 encoding
- I see. There are other regexp based code similar to what `Psych::Visitors::YAMLTree.visit_String` does. Not sure if testing for encoding before matching as I initially proposed is the way to go. What else do you suggest that could be a f...
-
10:04 PM Bug #15718: YAML raises error when dumping strings with UTF32 encoding
- rubenochiavone (Ruben Chiavone) wrote:
> Since it relates to mismatch of regex and YAML text encoding a possible fix is to only attempt to match the text when encoding matches or when text encoding is `ascii_compatible?`. WDYT?
What ... -
- Since it relates to mismatch of regex and YAML text encoding a possible fix is to only attempt to match the text when encoding matches or when text encoding is `ascii_compatible?`. WDYT?
Still I'm not sure why on other versions it wor... -
- It may be related to a code range bug.
By adding `o.valid_encoding?` to `Psych::Visitors::YAMLTree#visit_String`, the error raises in ruby 24 too. -
- ```ruby
module M1
refine Kernel do
def foo
'foo called!'
end
end
end
module M2
refine Kernel do
def bar
'bar called!'
end
end
end
using M1
puts foo
puts bar
```
Expected:
... -
04:24 PM Feature #15628: init_inetsock_internal should fallback to IPv4 if IPv6 is unreachable
- > Net:HTTP with timeout (Net::OpenTimeout) after after 60 seconds
I meant "Net:HTTP will timeout (Net::OpenTimeout) after 60 seconds".
Any suggestion on fixing this would very helpful 
01:32 PM Bug #15649 (Closed): Dir.glob regression with braces and Windows drive letters - Applied in changeset trunk|r67332.
----------
dir.c: fix Dir.glob starts with brace
* dir.c (ruby_glob0): expand braces if a glob pattern starts with
brace.
[ruby-core:91728] [Bug #15649] -
01:32 PM Revision 0f63d961 (git): dir.c: fix Dir.glob starts with brace
- * dir.c (ruby_glob0): expand braces if a glob pattern starts with
brace.
[ruby-core:91728] [Bug #15649]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67332 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67331 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- to avoid inlining a method call when it becomes argument_arity_error,
fixing a potential bug.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67330 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67329 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- ありがとうございます。とりあえず明らかな型バグがあったので修正しました。
```
$ ./miniruby /tmp/test.rb
Traceback (most recent call last):
1: from /tmp/test.rb:in `each'
/tmp/test.rb:3:in `foo': error! (RuntimeError)
```
↑のように、嘘の行番号は出なくなりました。 -
- Applied in changeset trunk|r67326.
----------
Fix a wrong lineno in backtrace for cfunc
lineno is an int, and INT2FIX(0) was assigned.
[Bug #15719] [ruby-core:91911] -
03:13 AM Bug #15719 (Closed): to_enum を使用した場合にバックトレースが意図しないものになる
- to_enum を使用するとバックトレースの呼び出し元が実行ファイルの1行目 each と出力されます。
再現コードの 8 行目や、to_enum に指定した foo メソッドがバックトレースに出てくるべきかと思います。
### 再現コード
```ruby
def foo
return to_enum(__method__) unless block_given?
raise 'error!'
yield 1
end
enum ... -
- because it's not used outside vm*.c, and also having non-static function
without MJIT_STATIC is harmful for mswin JIT system.
I hope this fix mswin test failure starting from r67315.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67... - 05:59 AM Revision 3c4b7898 (git): * expand tabs.
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67327 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- lineno is an int, and INT2FIX(0) was assigned.
[Bug #15719] [ruby-core:91911]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67326 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- because stderr did not have sufficient information
https://ci.appveyor.com/project/ruby/ruby/builds/23242505/job/dirugxujk70nnhp6
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67325 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- ```
To prevent this, a new "pinning" table was introduced. Any object marked via
rb_gc_mark is "pinned" and is not allowed to move. C extensions must mark
their references in order to keep them alive. Since C extensions use
rb_gc_mar... -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67324 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- I forgot to explain it in the previous commit
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67323 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67322 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
03:24 AM Revision 7aacb650 (git): Remove duplicated and change order
- `reg*` affects `doc/regexp.rdoc`, but it is not a file of the Oniguruma/Onigmo regular expression engine.
`reg*.[ch]` matches `reg*` except `doc/regexp.rdoc`.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67321 b2dd03c8-39d4-4d8f-98... -
- Eregon (Benoit Daloze) wrote:
> The same as "1 byte hash value".
> ...
I think so. I'm unsure how may people encounter this incompatibility.
```
class Foo
def hash
$hash
end
end
obj = Foo.new
h = {}
$hash = 0
h[o... -
- What version of DateTime do you use?
With the trunk I got:
```ruby
require 'date'
dt1 = DateTime.new(2001, 2, 3)
dt2 = DateTime.new(2001, 2, 3, 12)
p dt1 === dt2 #=> true
p dt1 == dt2 #=> false
``` -
-
- microweb10 (Julian Herrero) wrote:
> I would like to work on this one.
Please do, patches are always welcome. -
- I have verified that with the beta files for Unicode Version 12.1.0 at https://www.unicode.org/Public/12.1.0/ucd/, Ruby compiles and runs all tests (make check) successfully.
Please note that different from other betas, this beta uses... -
-
- ファイルの存在は確認できた、ということで閉じます。何かアクションがある場合は Status 戻して進めてください。
03/20/2019
-
-
- Applied in changeset trunk|r67320.
----------
Add Enumerator::Lazy docs.
* explanation of the class concept, with examples;
* docs for all class methods (most of them just say "Like Enumerable#<methodname>, but chains operation to ... -
- * explanation of the class concept, with examples;
* docs for all class methods (most of them just say "Like Enumerable#<methodname>, but chains operation to be lazy-evaluated.", but I believe they are useful this way because now have ... -
- I couldn't reproduce this with Mojave.
```
~ > ls /usr/include/netinet6/in6.h
/usr/include/netinet6/in6.h
```
It seems your development environment issue. -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67319 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67318 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- ```shell
ruby -r yaml -e "p YAML.dump( ''.force_encoding('UTF-32LE') )"
Traceback (most recent call last):
4: from -e:1:in `<main>'
3: from /Users/work/.rvm/rubies/ruby-2.6.1/lib/ruby/2.6.0/psych.rb:513:in `dump'
2: from /Users... - 07:57 PM Revision 02df0f38 (git): * 2019-03-21
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67317 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
- 07:57 PM Revision 5c439ebf (git): * expand tabs.
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67316 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- There is a special optimization for "only lead parameters"
method dispatch using specialized dispatcher functions
`vm_call_iseq_setup_normal_0start...`.
Other cases (opt, rest, post, ...) we don't use specialized
dispatcher and call with... -
- There is a commit that claims to backport #15270, `ruby_2_5@66225` / `aba207b7620d963e212e4187213db7e1eee7a790 `.
However, the patch in #15270 wasn't actually backported. For reference, here is a script that outputs
```
"2.6.2"
3... -
05:31 PM Feature #13677: Add more details to error "Name or service not known (SocketError)"
- shyouhei (Shyouhei Urabe) wrote:
> The proposed functionality sounds fine but no one currently have spare time to implement this; patch welcomed.
I would like to work on this one. -
01:30 PM Feature #15663: Documenting autoload semantics
- Eregon (Benoit Daloze) wrote:
> I was thinking maybe the require lock per path should be used for everything, but then since #autoload calls `require` dynamically, how to keep track which thread is loading the constant and so should o... -
- akr (Akira Tanaka) wrote:
> Eregon (Benoit Daloze) wrote:
> ...
It seems tricky implementation-wise, constant resolution (e.g. #const_get) has the constant data structure, and #require has the expanded file path + related lock but none... -
- akr (Akira Tanaka) wrote:
> > Could we start a document specifying the semantics?
> ...
Of course, there is no problem to describe the single thread semantics. -
- Eregon (Benoit Daloze) wrote:
> I would have thought `require autoload_path` would basically do the same as triggering the autoload of the constant (such as `Foo`). But the results above show they differ.
Agreed.
I think no one ... -
-
- @headius Could you attach a diff for the weakref-based approach?
It seems the GitHub link doesn't work well (it shows the list of commits for me). -
- @seki
Can you handle this?
-
- Well, as @shyouhei described, daily builds are testing wider range of environments which we do not want for every commit. As the original title "Duplicate builds on travis-ci?" and the description "This seems unnecessary" were wrong, I r...
-
- I removed CRON jobs from Travis CI.
-
- Eregon (Benoit Daloze) wrote:
> Should this "global autoload lock" also be locked for normal non-autoload `require`?
I think requiring a library which is configured for autoload should lock "global autoload lock".
Currently I think ... -
- Should this "global autoload lock" also be locked for normal non-autoload `require`?
Otherwise I think it could deadlock:
```
T1: require "foo"; AutoloadC;
T2: AutoloadC; require "foo";
``` -
- Made some changes for "auto compaction"
I am a newbie in C programming
This is just for discussion, not tested nor compiled yet
https://github.com/ruby/ruby/compare/trunk...PikachuEXE:feature/gc-compact/pika
-
-
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67314 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- Applied in changeset trunk|r67313.
----------
Improve TracePoint docs.
* Mention new :script_compiled event;
* Deduplicate __enable/enable methods;
* Document target: and target_line: arguments.
[Bug #15484][ruby-core:90801]
... -
- * Mention new :script_compiled event;
* Deduplicate __enable/enable methods;
* Document target: and target_line: arguments.
[Bug #15484][ruby-core:90801]
Co-authored-by: zverok <zverok.offline@gmail.com>
git-svn-id: svn+ssh://... -
- I created a patch.
> I would like to get this patch tested side-by-side at Discourse, GitHub and Shopify.
Could you test the patch attached? -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67312 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- I created a patch for the bug.
-
- * string.c: remove
-
-
- 僕が決められるのかわかりませんが、5年以上経っているので消していいと思います。
-
- I was also unable to reproduce.
```
~ > docker run --rm -ti alpine
/ # apk update
/ # apk add ruby-irb
/ # ruby -v
ruby 2.5.3p105 (2018-10-18 revision 65156) [x86_64-linux-musl]
```
-
-
- * string.c (rb_str_crypt): fix indent not to make the whole list
verbatim entirely.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67310 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
-
- The next meeting issue is here: https://bugs.ruby-lang.org/issues/15459
- 12:31 AM Revision eee58ca6 (git): * 2019-03-20
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67309 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67308 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
03/19/2019
-
- Sorry, your inconvenience experience. We have an issue of bugs.ruby-lang.org. I fixed it on this morning(JST).
I removed duplicated issues and copy from them.
@nobu said:
Intended.
It equals
```ruby
a.map{|x,| x} # => [1, 2, ... -
- > Honestly, I'm not a fan of the behavior, though.
I think it comes down a lot to personal preferences. For example I actually
like being able to use @NUMBER_HERE :) - although in "production" code,
I may use the oldschool variant s... -
- Yes, it is actually intended. `@1` is equivalent to `|at1, at2, at3, ...|`'s `at1`.
```
a = [1, 2, 3]
a.map{|x,| x} # => [1, 2, 3]
a.map{@1} # => [1, 2, 3]
a = [[1], [2], [3]]
a.map{|x,| x} # => [1, 2, 3]
a.map{@1} # => [1, 2... -
- In the following, `@1` refers to the entire item iterated:
```ruby
a = [1, 2, 3]
a.map{|x| x} # => [1, 2, 3]
a.map{@1} # => [1, 2, 3]
```
whereas in the following, `@1` refers to the first item achieved by decomposing the item ... -
- @localhostdotdev
I fixed an issue of our tracker. I deleted 15713-15716. -
- DateTime#=== is inherited from Date#=== without overwriting the #=== method, this leads to DateTime#=== comparing only dates and ignore the time part.
```
DateTime.new(2001, 2, 3) === DateTime.new(2001, 2, 3, 12)
=> false
```
I ... -
05:42 PM Feature #15667: Introduce malloc_trim(0) in full gc cycles
- As a maintainer of the quoted glibc code I'd be really interested in the results of this work. Please share when ready.
-
05:12 PM Bug #15711: Remove use of _id2ref from DRb
- Ok, unfortunately I'm not sure that WeakMap will work for this purpose. It works based on identity (which would not work in implementations where Fixnum-ranged Integers are not guaranteed to be the same object every time), attempts to at...
-
- I added a mutex and pushed the base implementation as a PR here: https://github.com/ruby/ruby/pull/2102
I can try to work up patches for the other two implementations, but they'll need some additional work within MRI to support. -
- We almost had agreement on adding a reference queue here: https://bugs.ruby-lang.org/issues/6309
-
- This issue relates to https://bugs.ruby-lang.org/issues/15408
DRb uses `_idref` internally to implement a weak map, and this issue seeks to replace that code with an implementation that does not use `_id2ref`.
We will be deprecatin... -
- Sorry for the delay folks, I was intermittently blocked from accessing bugs.ruby-lang.org, but things are working now!
I'll move forward with fixing DRb using the logic JRuby ships in https://bugs.ruby-lang.org/issues/15711.
Remain... -
- We have already discussed in https://bugs.ruby-lang.org/issues/15408 the deprecation and eventual removal of _id2ref, so perhaps we can move these things together.
The additional hashing logic to maintain the Object-to-ID maps will ad... -
- nateberkopec (Nate Berkopec) wrote:
> > Can we introduce it just after every major (full) gc?
> ...
As an experimental feature shouldn't it be disabled by default and only enabled via something like env variable?
But I do agree that... -
- Hanmac (Hans Mackowiak) wrote:
> Duplicate of #15620
It is irrelevant. -
- Another crash after updating to 2.6.2
ruby 2.6.2p47 (2019-03-13 revision 67232) [x86_64-darwin18]
Not sure they are related to the same issue
```
Process: ruby [42621]
Path: /Users/USER/*/ruby
Ident... -
07:03 AM Bug #15620: Block argument usage affects lambda semantic
- @nobu should this one be closed too?
-
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67307 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- Applied in changeset trunk|r67306.
----------
parse.y: fix var_ref of numbered param in ripper
* parse.y (string_dvar, user_variable): register numbered
parameter in ripper for var_ref.
[ruby-core:91867] [Bug #15673] -
- * parse.y (string_dvar, user_variable): register numbered
parameter in ripper for var_ref.
[ruby-core:91867] [Bug #15673]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67306 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- * parse.y (parser_token_value_print): in ripper, ID values are
wrapped in NODE_RIPPER at set_yylval_name(), so print the Symbol
wrapped together.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67305 b2dd03c8-39d4-4d8f-98ff-823fe6... -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67304 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
01:39 AM Bug #15675 (Closed): "fatal - exception reentered" error after installing Ruby 2.5.5
- At first I have 2.5.3 and 2.6.0 which are working fine. Then I started to encounter errors in Heroku after deployment, I tried installing Ruby 2.5.5 since that is the supported version in Heroku in order to replicate the problem. After t...