Activity
From 04/17/2020 to 04/23/2020
04/23/2020
-
09:49 PM Bug #16813 (Closed): Incorrect and Duplicated Method Docs - 2.6.1-core through 2.7.1-core
- ## https://ruby-doc.org/core-2.7.1/Method.html#method-i-5B-5D
`meth[args, ...] → obj` has the correct explanation, but contains the example for `#call` instead of `#[]`
## https://ruby-doc.org/core-2.7.1/Method.html#method-i-3E-3E
`... -
08:44 PM Feature #16812: Allow slicing arrays with ArithmeticSequence
- @Eregon, I wanted at first to see what people say about this one :)
`Array#[]=` is a thing that should be kinda "symmetric", but playing a bit with it, I understood that I am afraid of trying to guess what would be "logical".
Hon... -
08:04 PM Feature #16812: Allow slicing arrays with ArithmeticSequence
- Rather neutral on this, but would you want that to work for `Array#[]=` too?
I would be against `Array#[]=` as it's already so complicated and that would just make it a lot more so.
In `Array#[]` it's probably fine though. -
- I believe when concepts of ArithmeticSequence and `Range#%` were introduced, one of the main intended usages was array slicing in scientific data processing. So, it seems to make sense to allow this in `Array#[]`:
```ruby
ary[(5..20)... -
- * [Feature #16812] Allow slicing arrays with ArithmeticSequence (zverok)
* `ary[(5..20) % 2]`—each second element between 5 and 20
* `ary[(0..) % 3]`—each third element
* `ary[10.step(by: -1)]`—elements 10, 9, 8, 7 ....
* Pyt... -
03:20 PM Bug #16811 (Feedback): [NOTE] You may have encountered a bug in the Ruby interpreter or extension libraries. Bug reports are welcome. For details: http://www.ruby-lang.org/bugreport.html This application has requested the Runtime to terminate it in an unusual way. Please cont
- This appears to happen when loading fiddle:
```
C:\metasploit\ruby\bin\x64-msvcrt-ruby250.dll(rb_bug_context+0x6f) [0x0000000067F3B59F]
C:\metasploit\ruby\bin\x64-msvcrt-ruby250.dll(rb_check_safe_obj+0xd7) [0x00000000680257B7]
[0x0... -
03:01 PM Bug #16811 (Closed): [NOTE] You may have encountered a bug in the Ruby interpreter or extension libraries. Bug reports are welcome. For details: http://www.ruby-lang.org/bugreport.html This application has requested the Runtime to terminate it in an unusual way. Please cont
C:\metasploit>console.bat
C:/metasploit/apps/pro/vendor/bundle/ruby/2.5.0/gems/rb-readline-0.5.5/lib/rbreadline.rb:4434: [BUG] Illegal instruction
ruby 2.5.5p157 (2019-03-15 revision 67260) [x64-mingw32]
-- Control frame informati...-
01:19 PM Revision 0f5ae7a2 (git): Fixed inverted current thread condition [Bug #16808]
-
- Applied in changeset commit:git|a52a459b16ce1b5cf32cb6393960ff59e35c48d0.
----------
Truncate too long thread name before setting [Bug #16808] -
06:16 AM Bug #16808 (Closed): Thread#name= only accepts up to 15 characters with Linux/pthread implementation
- Repro:
irb(main):001:0> RUBY_VERSION
=> "2.7.1"
irb(main):002:0> Thread.new { Thread.current.name = 'abcdefg'; sleep }
=> #<Thread:0x000055584a17e1c8 (irb):2 run>
irb(main):003:0> Thread.new { Thread.current.name = 'abcdefghijklmn... -
-
12:11 PM Revision 03e4eeab (git): Skip the initialization of XDG_DATA_HOME with Permission denied
-
10:45 AM Bug #16787: [patch] allow Dir.home to work for non-login procs when $HOME not set
- Attaching version "v6" of the patch, which is just another WIP milestone.
Please do not spend too much time with this version -- I'm mainly just documenting where I am currently because I haven't had much time to look at this the last f... -
- * Support XDG_CONFIG_HOME for gemrc.
* Support XDG_DATA_HOME for .gem
* Added test for XDG_DATA_HOME
* Do not reuse environmental variable.
* Unify .rdoc path to RDoc.home.
* Support XDG_DATA_HOME for .rdoc
* Ignore exists?
* Extr... -
- ko1 (Koichi Sasada) wrote in #note-8:
> My conclusion is it is bad idea to share the same code between interpreters.
I believe any alternative Ruby implementation would tell you the opposite: the more shared code the less duplicated ... -
05:53 AM Feature #16254 (Assigned): MRI internal: Define built-in classes in Ruby with `__intrinsic__` syntax
- Eregon:
There are two poionts: (1) sharing the code between Ruby implementations and (2) prettier syntax.
# (1) sharing the code between Ruby implementations
I assume it is using same `.rb` code between Ruby implementations.
My conclu... -
08:49 AM Bug #16810 (Closed): ruby segfaults on s390x with musl libc
- When trying to build mruby-2.1.0 ruby segfaults when running `ruby ./minirake -v`.
I was able to get a backtrace with gdb:
```
Program received signal SIGSEGV, Segmentation fault. ... -
08:46 AM Revision f563f3c5 (git): RDoc enhancements for Hash[].
-
08:30 AM Misc #16803: Discussion: those internal macros reside in public API headers
- Eregon (Benoit Daloze) wrote in #note-1:
> Could you give some pointers or example of other macros introduced in that change?
> ...
Almost every new macros are for portability. For instance `RUBY3_HAS_BUILTIN` is another macro that go... -
- This is still an issue for alpine s390x. See #16809
-
- ```
./revision.h unchanged ... -
- * `RbConfig::CONFIG['ridir']` has been set since 1.9.2
* `ENV["HOME"]` has been defaulted to `USERPROFILE` since 1.9.0,
and backported to 1.8.5 or later.
https://github.com/ruby/rdoc/commit/a3a614e676 -
06:10 AM Feature #16806: Struct#initialize accepts keyword arguments too by default
- I agreed with your ideas and reflected them to the description.
-
-
- As well as worker processes do in Test::Unit::Worker#run.
-
-
-
04/22/2020
-
10:41 PM Bug #16669: Rails Action Text unit tests fail since b9007b6c548f91e88fd3f2ffa23de740431fa969
- I have confirmed `ruby 2.8.0dev (2020-04-22T17:21:38Z master 8119bcbfc0) [x86_64-darwin19]` addresses Rails Action View unit test failures/errors. Thank you.
-
- Applied in changeset commit:git|8119bcbfc04772fe4012b5ed396a68f02e312316.
----------
rb_method_entry() returns valid me.
search_method() can return invalid method, but vm_defined() checks
it as valid method entry. This is why defined?(... -
- search_method() can return invalid method, but vm_defined() checks
it as valid method entry. This is why defined?(foo) if foo is undef'ed.
To solve this problem, check invalidation and return NULL.
[Bug #16669]
https://twitter.com/kamipo... - 04:41 PM Revision 492e8599 (git): * 2020-04-23 [ci skip]
-
04:40 PM Revision 6292271e (git): Fix permission of PATH
- https://github.com/ruby/actions/runs/608526685?check_suite_focus=true
`warning: Insecure world writable dir /home/runner/.config in PATH, mode 040777` -
03:41 PM Bug #16804: Vagrant Up does not work anymore
- Please close this. Thank you.
-
- Thank you Jeremy Evans for pointing me to the right direction. I found workaround in one of your links (https://github.com/hashicorp/vagrant/issues/11492) - downgrading Vagrant version.
-
- I'm OK with the basic idea of allowing keyword init for Structs by default. However, because this changes behavior, I think we should keep existing behavior and warn in Ruby 3.0 and not make this change until Ruby 3.1. I think this chan...
-
- ## Proposal
```rb
Post = Struct.new(:id, :name)
# In addition to this,
Post.new(1, "hello") #=> #<struct Post id=1, name="hello">
# Let the following initialization also work
Post.new(id: 1, name: "hello") #=> #<struct Post i... -
- Even for empty argument list, not to be confusing with a writer
method name. -
-
- This reverts commit 67bcac879a2e0ddfb4e7bbd7cb5e5401422de76a.
-
- `ID` list in `NODE_SCOPE` seems corrupted.
Maybe a GC compaction related issue?
-
08:03 AM Bug #16807 (Closed): Ruby 2.7 segfault loading sources under GC.stress
- Originally seen in https://github.com/protocolbuffers/protobuf/pull/7386, but reproduces without C extension.
Reproduction: place these four files from [this gist](https://gist.github.com/qnighy/099a39e70e66d8b402b193d4b0471aee):
-... -
08:21 AM Misc #16747: Repository reorganization request
- It should include also better place for default gems:
https://bugs.ruby-lang.org/issues/16778
And also it would be nice if all vendored/bundled code is in dedicated directory if possible, e.g. libraries taken from ccan, onigmo, rub... -
- With https://bugs.ruby-lang.org/issues/16254, We should re-organize the top-directory before increasing the files like kernel.c and kernel.rb.
-
-
06:53 AM Misc #16802 (Closed): Prefer use of RHS assigment in documentation
- Okay great. For now, I'm satisfied we don't use this in documentation. However if we adopt it I'll consider it again.
-
- This reverts commit 6b04c480487ab64d73e1254be2412e722b7b8bd8.
Trailing spaces separate paragraphs in RDoc format. -
01:19 AM Feature #8661: Add option to print backtrace in reverse order (stack frames first and error last)
- I agree with `--backtrace-limit`, and actually I use `rb_backtrace_length_limit` in my patch :-)
I'll update my patch if I get a reply from matz. -
12:34 AM Feature #8661 (Assigned): Add option to print backtrace in reverse order (stack frames first and error last)
- jeremyevans0 (Jeremy Evans) wrote in #note-37:
> I agree the option could have a better name. I recommend `--backtrace-limit`, as that indicates a numerical setting, as opposed to `--show-backtrace` or `--print-backtrace`, both of wh... -
-
12:49 AM Revision 17083011 (git): support builtin for Kernel#Float
- # Iteration per second (i/s)
| |compare-ruby|built-ruby|
|:------------|-----------:|---------:|
|float | 30.395M| 38.314M|
| | -| 1.26x|
|float_true | 3.833M| 27.322M|
| ...
04/21/2020
-
- duerst (Martin Dürst) wrote in #note-36:
> I think the option's name (`--suppress-backtrace`) is wrong. If I write `--suppress-backtrace=10`, it reads like "suppress 10 entries of backtrace". That would mean if the whole backtrace is 50... -
- I think the option's name (`--suppress-backtrace`) is wrong. If I write `--suppress-backtrace=10`, it reads like "suppress 10 entries of backtrace". That would mean if the whole backtrace is 50 entries, it would print 40 entries. The nam...
-
- Applied in changeset ruby-master:commit:git|bf11bf31e2e795bb22c939a5b5cd412c98208982.
----------
NEWS.md: the order of backtrace [Feature #8661] [ci skip] -
- I've created a PR for `--suppress-backtrace=num` option.
https://github.com/ruby/ruby/pull/3047
@matz Could you confirm if the behavior is right as you think?
t.rb
```ruby
def f1 = raise
def f2 = f1
def f3 = f2
def f4 = f3
... -
- Reopen because we need to support `--suppress-backtrace=5`.
-
- Applied in changeset ruby-master:commit:git|487d0c99d53208594702bb3ce1c657130fb8d65f.
----------
eval_error.c: revert the "reversed" backtrace [Feature #8661]
Now, the order is good, old-fashioned style:
```
$ ./local/bin/ruby -e 'def... -
08:17 AM Feature #8661: Add option to print backtrace in reverse order (stack frames first and error last)
- Thank you @matz!
I can try to prepare patch including both options:
1. specify order
2. limit amount of lines printed -
-
- Thank you very much, @matz!!!
-
07:53 AM Feature #8661: Add option to print backtrace in reverse order (stack frames first and error last)
- OK, let's revert it. Instead, I want to something to suppress backtrace lines (e.g. `--suppress-backtrace=5` command-line option to `ruby` or something similar in `RUBYOPT` environment variable).
Matz.
-
- ioquatix (Samuel Williams) wrote in #note-6:
> Oh okay, I thought it was a sure thing at this point - where is the experimental nature of it being tracked?
It's mentioned in NEWS.md. Both rightward assignment and endless method defi... -
- Oh okay, I thought it was a sure thing at this point - where is the experimental nature of it being tracked?
-
10:06 PM Misc #16802: Prefer use of RHS assigment in documentation
- Eregon (Benoit Daloze) wrote in #note-4:
> I think we should wait that RHS assignment is no longer experimental.
> ...
I agree and I’m not a big fan either. It seems to me that for some time there’s been accepting and immediately merging... -
- I think we should wait that RHS assignment is no longer experimental.
As I see it, it might get similar backlash as the pipeline operator and might still be removed (personally I don't like RHS assignment, I find it confusing and less... -
- I'm not sure it's a good idea. There's some value in distinguishing between an actual right-hand-side assignment and the resulting value of an expression (where expression includes right-hand-side assignments :-).
Also, as far as I un... -
- @matz do you mind letting me know your thoughts?
-
- Many documentation uses some format like this:
```
Hash.new -> hash
```
Now that RHS assignment is a thing, we can make the documentation valid Ruby code:
```
Hash.new => hash
```
There is some d... -
- I think as much as feasible macros accessing internals should not be in public headers.
OTOH, I think macros purely for portability between platforms, compilers, C/C++ compatibility are fine.
`RUBY3_STATIC_ASSERT` seems harmless (jus... -
- A while ago I merged https://github.com/ruby/ruby/pull/2991 ("Split ruby.h"). This seems working. But the changeset raised several questions.
The biggest one relates to those newly publicised macros and inline functions. For instan... -
- as well as e62aead26909e83f2c8b940186047f0a88b9f2d6
-
- 05:05 PM Revision cebf575d (git): * 2020-04-22 [ci skip]
-
- Since it is impossible to detect stack overflow of C functions robustly,
the test is a bit unreasonable.
https://rubyci.org/logs/rubyci.s3.amazonaws.com/debian-riscv64/ruby-master/log/20200421T120018Z.fail.html.gz -
- hshimoyama (Hiroyasu Shimoyama) wrote in #note-24:
> I tried to reproduce this issue, but it was not reproduced today.
> ...
It works because the docker library image is using my patch:
https://github.com/docker-library/ruby/blob/ma... -
- This appears to be a bug in Vagrant:
* https://github.com/hashicorp/vagrant/issues/11497
* https://github.com/hashicorp/vagrant/issues/11492
-
- Good day,
I was able to set up a VM (Scotch Box Pro @ https://github.com/scotch-io/scotch-box) last week and it was successful; I didn't encounter any ruby bug or hints.
Yesterday, I updated VirtualBox and Vagrant, and created a diff... -
- 12:12 PM Revision 6b04c480 (git): * remove trailing spaces. [ci skip]
-
-
-
-
10:37 AM Bug #16797: Array#flatten not checking `respond_to? :to_ary`
- nobu (Nobuyoshi Nakada) wrote in #note-1:
> Read the error message.
> ...
Read what I wrote:
> It should check whether an object responds to to_ary before trying to convert it into an array.
I know it used `to_ary` method and got a... -
-
-
- Files under `coroutine/` start like this:
```C
/*
* This file is part of the "Coroutine" project and released under the MIT License.
*
```
The problem is, there is no definition of "the MIT License" throughout the entire pro... -
- Now, the order is good, old-fashioned style:
```
$ ./local/bin/ruby -e 'def foo; raise; end
def bar; foo; end
def baz; bar; end
def qux; baz; end
qux
'
-e:1:in `foo': unhandled exception
from -e:2:in `bar'
from -e:3:in `... -
- Can I have any answer for my question ("Is this intentional?")?
-
- Ditto for adab82b9a71f60ad1c7f4f8c134a5ae9198ab32a. TRY_WITH_GC was
found innocent. -
-
- NDEBUG can be defined via a command-line argument. Should take care of
such situations. -
- Ditto for 4b853932eaa7fa4acf8a0f0c9b7c695bb4f5e76d
-
- NoMemoryError is observed on icc but I fail to reproduce so far. Let me
see the backtrace on CI. -
-
- In order to experiment with this, I'd like to propose the following hooks to the scheduler:
```ruby
class Scheduler
# A fiber has tried to lock a mutex, but it failed.
def wait_mutex(mutex)
end
# A mutex which has pre... -
- Here is a quick hack I used to add `Fiber.backtrace` to aid in debugging. I'd say, don't use it in production, but I did :p
```ruby
module Fiber::Backtrace
def yield
Fiber.current.backtrace = caller
super
end
end
class ...
04/20/2020
-
- https://github.com/ruby/ruby/pull/2580 is already closed.
-
- I added the workaround for man path with ruby installation. But we should care about the convention of Linux distribution.
Welcome to additional patches. -
- Applied in changeset commit:git|b9962f0e8909b1163320fbcfe80060a259b2353d.
----------
Fixed incorrect man path with ruby installation path
[Bug #15359][ruby-core:90164] -
- [Bug #15359][ruby-core:90164]
-
06:02 PM Feature #15921: R-assign (rightward-assignment) operator
- Ah right, trying the master branch is the fastest way to get answers, duh. But this brings me to this little surprise:
```ruby
5 + 3 => x #=> 8
5 + 3 => x.to_s #=> undefined method `to_s=' for 8:Integer
5 + 3 => x
.to_s #... -
- In current head, it is so:
```ruby
x1 = 5 + 3 => y1
p [x1, y1] # [8, 8]
5 + 3 => x2 => y2
p [x2, y2] # [8, 8]
*[1, 2, 3] => x3, y3
# ^ syntax error, unexpected =>, expecting '.' or &. or :: or '['
[1, 2, 3] => x4, y4
p [x4,... -
- I'd like to hear some clarifications on the expected behavior of rightward assignment.
assignment at both ends? `x = expr => y`
multiple assignment? `expr => x => y`
splatted assignment? `*expr => x,y`
auto-splatted assignment? `expr =>... -
- https://rubyci.org/logs/rubyci.s3.amazonaws.com/debian-riscv64/ruby-master/log/20200420T083601Z.fail.html.gz
- 03:00 PM Revision 7a0ac279 (git): * 2020-04-21 [ci skip]
-
- Currently, objdump -W miniruby emits some errors on riscv, so I guess
that DWARF is corrupted. -
- byroot (Jean Boussier) wrote in #note-3:
> To clarify, what I'm trying to say is that the `"new"` method should simply forward everything to the `initialize` method no matter what. I can't see any reason for `Struct#new` to have arbitra... -
02:20 PM Bug #16801: The default Struct constructor improperly handle keyword arguments
- To clarify, what I'm trying to say is that the `"new"` method should simply forward everything to the `initialize` method no matter what. I can't see any reason for `Struct#new` to have arbitrary restrictions.
-
- @jeremyevans0 I'm afraid I don't understand what you are referring to:
2.7.1:
```
$ ruby -v
ruby 2.7.1p83 (2020-03-31 revision a0c7c23c9c) [x86_64-darwin19]
$ ruby --disable-gems -e 'p Struct.new(:hash_value).new(hash_key: 1)'
... -
- I think the something your missing is this would break existing code:
```ruby
Struct.new(:hash_value).new(hash_key: 1)
```
Treating the keywords as named columns when they were originally designed to be a hash value for the next ... -
- Reproduction script:
```ruby
Field = Struct.new(:value) do
def initialize(value, keyword: false)
super(value)
@keyword = keyword
end
end
Field.new(1, keyword: true)
```
```
/tmp/kw.rb:8: warning: Using the la... -
-
- [ci skip]
-
-
-
- It is not a good idea to compare `exitstatus` with 0 from the point of portability.
I'd recommend to use `Process::Status#success?`.
Also if the exit code value is not important but succeeded or failed is just needed, `exit $?.success?... -
- Those short aliases are definitely a bad idea but I understand the OP's frustration with `$?` because it's different from the shell's `$?`. `Process::Status` has several methods that I'm sure can be useful in various circumstances, but t...
-
- In addition to matz's note, we had tried the single namespace once some years ago.
Finally we found that the incompatibility was much bigger than expected before, and abandoned. - 03:37 AM Revision b4c9b570 (git): * 2020-04-20 [ci skip]
-
- As atomic operations are mandatory now, not-working phony fallback
definitions are not only useless but confusing and harmful. -
- Actually what happens here is pretty interesting. This is all done via `rb_check_array_type` which attempts to convert an object by using `to_ary`.
If your object defines its _own_ `respond_to?` method, it is used to determine if `to_... -
- Great. Thank you.
-
- I believe that it is already fixed on master by the patch of #16774.
04/19/2020
-
- VMDEBUG is always defined as defaulted to 0 in vm_core.h.
- 02:38 PM Revision 73bd2b70 (git): Update VMDEBUG reference doc [ci skip]
- Since this commit (https://github.com/ruby/ruby/commit/9e1b06e17d27fb4ddf51e9244f205417e9c4dd5c), the VM Debug Level constant is moved from `vm_insnhelper.h` to `vm_core.h`. This PR is a super tiny update to reflect that change so that p...
-
- I'd love to enhance the language to be nice to functional programming but at the same time, we have to be nice to existing programs by keeping compatibility. Proposed new syntaxes are incompatible changes so that we cannot accept them.
... -
04:34 AM Feature #16799: Add more functional features,make ruby more friendly.
- Yes, changing the syntax is currently not a good choice, but I think it is necessary to modify the method call syntax to maintain the same form, and the method name is just a variable name (in order to support more flexible functional pr...
-
- ... just like AIX and OpenBSD.
-
- The test fails due to unknown reason. Need to debug in future, but
tentatively skipped. -
- According to that log, seems CAS is not available.
-
10:22 AM Bug #16800 (Closed): [riscv64-linux] miniruby: thread_pthread.c:1935: rb_sigwait_fd_put: Assertion `old == th' failed.
- The last version of Ruby in Fedora/RISCV is v2.5.7. It seems that anything above v2.5 series fails to build (tried multiple times with different releases over a long time).
All the builds fail the same:
```
[..]
./miniruby -I./lib ... -
- I agree on this is really unfortunate and annoying change. I need to go thru backtrace visually first to decide which order is used and then do second visual parsing to actually use it. The new order usually means I need to scroll up in ...
-
- Yes, this is still the most annoying change in Ruby. Once the backtrace is displayed in reverse order, the other time in normal order, depending if I am seeing log in TTY or in file. Terrible.
-
- I have not changed my opinion, but I gave up and now wrap every command with my own gem which puts it back in the top to bottom order.
-
- As for the pipeline operator, it could be more useful in combination with right assignment operators.
```ruby
foo(...).bar(...) => x
|> zot(...) => y
```
is same as
```ruby
y = (x = foo(...).bar(...))
.zot(...)
```
-
- So,in fact,only one pipeline operator is needed to call the method in reverse.
``` ruby
puts "hello world"
#Pipeline call
"hello world" |> puts
```
-
- hsbt (Hiroshi SHIBATA) wrote in #note-18:
> I and the maintainer of the default gems will extract the default gems to the bundled gems. After that, We dont't need to care the duplicated code.
Doesn't this mean ruby won't have stdlib ... -
- hsbt (Hiroshi SHIBATA) wrote in #note-18:
> 2. There is no plan to use git submodule for these issues. The ruby commiter can't push the master branch of the part of default gems contained rubygems. We need to push them for fixing CI of ... -
- This issues is too complex and complicated. I and mame and the maintainers of default gems already considered these topics.
1. Removing the default gems from ruby core repository, It's too hard to maintain with the changes of ruby inte... -
- @matz do you mind checking this when you have time? Especially `Fiber#backtrace` is super important for debugging issues with fibers.
-
- https://ci.appveyor.com/project/ruby/ruby/builds/32278754/job/90jmky2jq2k0wjv8
-
12:35 AM Revision c0b93267 (git): Update workflows/mingw.yml - use setup-ruby-pkgs (#3042)
- MSP-Greg/actions-ruby is deprecated...
04/18/2020
-
09:25 PM Feature #16799: Add more functional features,make ruby more friendly.
- method1 = (f,n) -> do
return f(n)
end
I think a syntax change such as this may be very problematic.
People would not typically expect this, and even if we, say, assume that this
may be a better syntax for newcomers... -
- Classes are currently first-class citizens in Ruby, but functions are not.
This leads to a situation where the function calls are not uniform, for example:
``` ruby
def boo(x)
return x
end
boo2 = -> x { x }
a = boo 10
b = boo2.... -
- * [Misc #16778] Should we stop vendoring default gems code? (greggzst)
* it makes maintenance easier and removes the need for synchronization
* removes confusion for external contributors
* Ruby uses git so git submodules could be ... -
05:17 PM Feature #16781: alias :fold :reduce
- 0x81000000 (/ /) wrote:
> 2. Name "fold" is more common/popular than "reduce" or "inject".
I was surprised to hear this, since I think of "reduce" as most popular. A quick survey of popular languages seems to confirm that "reduce" is... - 03:35 PM Revision cf332f68 (git): * 2020-04-19 [ci skip]
-
02:31 PM Bug #16776: Regression in coverage library
- marcandre (Marc-Andre Lafortune) wrote in #note-3:
> I never realized this limitation. I imagine that for the vast majority of users it's a non issue, but for `byebug` it is quite serious. Would you consider using `deep-cover` instead?
... -
- Thanks for the quick fix @nobu, and for setting the backports! <3
-
- Applied in changeset commit:git|08529a61153e5c40f57a65272211357511d6e6db.
----------
Compare environment variable names in those manor [Bug #16798] -
-
-
-
- Only the names are case-sensitive.
-
02:12 PM Revision db0d850d (git): [ruby/reline] Add ed_search_next_history
- https://github.com/ruby/reline/commit/ca750b676b
-
- https://github.com/ruby/reline/commit/e9ae288825
-
- https://github.com/ruby/reline/commit/8480db575b
-
- https://github.com/ruby/reline/commit/cab312f584
-
- https://github.com/ruby/reline/commit/d563063ea0
-
-
- Implicit assignment from regular expression matches has been a bad idea. I shouldn't have merged it at the first moment.
I'd like to remove it altogether if I have a chance. So I don't like to enhance it any further.
Matz.
-
11:42 AM Revision e042380e (git): power_assert repository is transferred to ruby/power_assert
-
- Read the error message.
```
-:4:in `flatten': can't convert Object to Array (Object#to_ary gives Object) (TypeError)
```
-
- on stack when local_stack_p is enabled.
This fixes `RB_FL_TEST_RAW:"RB_FL_ABLE(obj)"` assertion failure
on power_assert's test with JIT enabled. -
-
- Slightly simplifying 8d6aa06620b316904fd10d0cab1b85e07f2fbf67
-
- In the last 26-ish hours, it has failed 5 times:
https://travis-ci.org/github/ruby/ruby/jobs/676497718
https://travis-ci.org/github/ruby/ruby/jobs/676480295
https://travis-ci.org/github/ruby/ruby/jobs/676103216
https://travis-ci.org/gith... -
-
04/17/2020
-
- nobu (Nobuyoshi Nakada) wrote in #note-10:
> Thank you, I left some comments at the PR for the details.
> ...
Thanks; I'm taking a look now. -
- Thank you, I left some comments at the PR for the details.
IMHO, the new functions may fit more in process.c. -
- Attaching the "v5" version of the patch (for real this time).
-
- According to warnings on Travis, there's no such key. We handle this on
webhook side anyway. - 05:12 PM Revision 7c0bc724 (git): * 2020-04-18 [ci skip]
-
- We failed to ignore
https://ci.appveyor.com/project/ruby/ruby/builds/32245902/job/xcfxw67uexxysvni -
- sawa wrote:
> I have met such use cases, and agree this would be useful.
I don't disagree in the sense that there may be valid use cases,
but the syntax is kind of weird:
/s(?<mid>.)r/
I use regexes a lot of course, sinc... -
- sawa (Tsuyoshi Sawada) wrote in #note-2:
> Alternatively, in order to access even unnamed matches, assigning the last matched data to a variable with the following syntax may be useful.
> ...
That's too confusing. The following code w... -
10:20 AM Feature #16796: Assigning local variables when using `case when regexp`
- I have met such use cases, and agree this would be useful.
Alternatively, in order to access even unnamed matches, assigning the last matched data to a variable with the following syntax may be useful.
```ruby
case "str"
when /s(... -
- It is because `when` calls `===` method but not `=~`.
-
- I want to use
```ruby
case "str"
when /s(?<mid>.)r/
p mid
end
```
instead of
```ruby
case
when /s(?<mid>.)r/ =~ "str"
p mid
end
```
I also do not like using `$1`.
This feature is extremely useful when there are a lot... -
04:20 PM Bug #16788: T_CLASS counts classes double
- Thank you so much for the explanations @jeremyevans0 @Eregon!!!!
-
- Actually instead of using `|>` as the common element between rightward operators, maybe just the pipe character would be enough.
`|:` (because `|=` is taken)
`|~`
`|>`
`|>>`
`|**`
-
- It's an interesting idea. I am not sure if I can easily adjust to the syntax,
but this may be best to just ask matz directly (I think he suggested the
pipeline operator, and streem kind of also taps into that whole handling of
data id... -
01:22 PM Feature #16795: build ruby.exe on Windows against ruby-static.lib omitting x64-vcruntime-ruby.dll (no '--enable-shared' option for Windows)
- shevegen (Robert A. Heiler) wrote in #note-1:
> I feel you here. Not so much due to windows, but I totally understand every
> ...
just simple instructions how to build ruby.exe against static library instead of linking with x64-vcrunti... -
- I feel you here. Not so much due to windows, but I totally understand every
preference for --enable-shared and --enable static. :-)
Perhaps nobu and greg can help for the windows-related issues; perhaps greg
even through some automa... -
- On Windows, environment variable names are case insensitive:
```
PS C:\Users\deivi> ruby -e "puts ENV['Path']; ENV['PATH'] = 'foo'; puts ENV['Path']" ... -
- ```ruby
def (a = Object.new).method_missing(...)
Object.new
end
[a].flatten # TypeError
```
It should check whether an object responds to `to_ary` before trying to convert it into an array. -
-
-
- This is follow up of 62554ca97812b454e78a0a9daf6e962ff7a2f589
-
- Deprerecated constants which had been warned since 2.4.
-
- Tidy up proposal.
-
- Make `wait_readable`, `wait_writable` and `wait_any` take `IO` argument. Add explicit wrappers for CRuby.
-
- Instead of letting callers rescue the error always.
-
- * renamed argument `writable` as `waiting`
* hosited out creating and raising exception
* turned into a `switch` -
-
- @jeremyevans0 thanks so much for fixing this at least in the #include case.
-
- Just cast down explicitly.
-
- The user management on Android seems very different
https://rubyci.org/logs/rubyci.s3.amazonaws.com/android28-x86_64/ruby-master/log/20200416T234122Z.fail.html.gz