Activity
From 03/01/2020 to 03/07/2020
03/07/2020
-
11:40 PM Bug #16677: Negative integer powered (**) to a float number results in a complex
- Ah thanks for catching that.
Interesting, `-2 ** 2.2` is parsed as `-(2 ** 2.2)` whereas `-2.to_i ** 2.2` is parsed as `((-2).to_i) ** 2.2`.
It looks like whether it is a literal of negative two changes depending on the presence of the... -
06:12 PM Bug #16677: Negative integer powered (**) to a float number results in a complex
- > Negative integers are atomic tokens
If that was the case then `-2 ** 2.2` would be parsed as `(-2) ** 2.2`, which is not the case as shown above. -
- > So it looks like there's something special about how negative integers are parsed?
Negative integers are atomic tokens whereas the expression `-x` applies the unary `-` operator to `x`.
`-x.to_i` is parsed as `-(x.to_i)`:
```
$ ruby ... -
04:56 PM Bug #16677 (Open): Negative integer powered (**) to a float number results in a complex
-
- It's actually a bit more complicated than that.
```ruby
-2.to_i ** 2.2 #=> (3.717265962412589+2.7007518095995264i)
x = 2
-x.to_i ** 2.2 #=> -4.59479341998814
```
So it looks like there's something special about how negative int... -
02:25 PM Bug #16677 (Closed): Negative integer powered (**) to a float number results in a complex
- This is just operator precedence, ** has higher precedence than unary minus.
-
01:22 PM Bug #16677: Negative integer powered (**) to a float number results in a complex
- Oh sorry, I just notice that this is an expected behaviour in the documentation (example) given in Integer.
I guess the to-i attribute assignment is a bit confusing that it changes the behaviour but probably not a bug! -
- Not sure if this is an unexpected behavior.
This works as I expect:
```
-2 ** 2.2 # => -4.59479341998814
```
But when I change the code a bit, it gives me a complex:
```ruby
-2.to_i ** 2.2 # => (3.717265962412589+2.7007518... -
11:06 PM Bug #16681 (Closed): Backport commit related libffi url
- Please backport the following commits for fixing download error of libffi.
https://rubyci.org/logs/rubyci.s3.amazonaws.com/debian8/ruby-2.7/log/20200307T214956Z.fail.html.gz
* 47a1872cd8 : Use osuosl instead of GitHub releases
* 8... -
-
05:59 PM Bug #16462: Ruby 2.7 autoload not working with $RUBYLIB (maybe circular dependency error)
- Sorry for confusing, i find the really reason caused this issue, i will create a new issue #16680 for make reproduce more clearly.
I don't know how to close this issue, can you help on this?
-
- The following is a full reproducible process. I will use a gem named 'looksee' to reproduce this.
1. Do `gem install looksee`
2. Go to `gem` folder and copy `lib` content into `/tmp/test_looksee` so that we have a folder like this:... -
02:29 PM Bug #16679 (Closed): Test of Ruby fails under multiple OS user userland installations
- I do user land installations where each of multiple installations of a complex system under it's own OS user installs it's own version of tools from sources if the OS installed version doesn't match necessary criteria.
The system has to... -
- You can easily achieve wrap-around behavior with:
```ruby
> (1..5).to_a.values_at(*(-1..3))
=> [5, 1, 2, 3, 4]
```
Using a Range for `values_at` is like taking a slice with `Array#[]/slice`, and Array slices never wrap around (a g... -
10:42 AM Misc #16678: Array#values_at has unintuitive behavior when supplied a range starting with negative index
- Actually .values_at() confused me when I tried to use my go-to method for
obtaining a slice from an Array:
a[3..5] # => [4, 5]
There I wondered why it did not return the same. :-)
But anyway; I believe the question is what... -
06:21 AM Misc #16678 (Open): Array#values_at has unintuitive behavior when supplied a range starting with negative index
- Consider the following:
``` ruby
# frozen_string_literal: true
a = (1..5).to_a
p a.values_at(3..5) # => [4, 5, nil]
p a.values_at(-1..3) # => []
```
When the range begins with a negative `(-1, 0, 1, 2, 3)`, it returns an ... -
- Because the package provided by GitHub releases is different from sourceware.
-
-
10:06 AM Revision ada2f71c (git): rb_check_safe_obj no longer exists
- Commit e91c39f1c0f7d5e670266d9593d533fd444957f6 deleted definition of it.
Though I'm not sure if we can delete public API like this, it no longer
works nontheless. Having declaration without definiton is worse than
having nothing at all... -
10:03 AM Bug #16138: Backport Struct.new empty option hash fix to 2.5 and 2.6
- ruby_2_6 r67841 merged revision(s) 77596fb7a91cc119b25ac9e19b3c8682709765b4.
-
- Do not turn on keyword_init for Struct subclass if keyword hash is
empty
This was accidentally turned on because there was no checking for
Qundef.
Also, since only a single keyword is currently supporte... -
- ruby_2_6 r67840 merged revision(s) c4794ed73ad348a61a7cfbe3da0a7eb49ba46eb9.
-
- Avoid jumping to a wrong destination
when the next insn is already compiled by former branches.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/branches/ruby_2_6@67840 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- ruby_2_6 r67839 merged revision(s) 6e6844320de989cb88a154e2ac75066ccea1bba2.
-
- Fixed duplicated warning
As `command_rhs` is always a "value expression", `command_asgn`
does not need the same check.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/branches/ruby_2_6@67839 b2dd03c8-39d4-4d8f-98ff-823fe69b... -
- ruby_2_6 r67838 merged revision(s) 4f19666e8b144600e959e4673f79d63f98bd637d.
-
- backported into ruby_2_7 was done at db4d136889afbf59e69efcfd495fd91cd401f378.
-
- `Regexp` in `MatchData` can be `nil`
`String#sub` with a string pattern defers creating a `Regexp`
until `MatchData#regexp` creates a `Regexp` from the matched
string. `Regexp#last_match(group_name)` accessed it... -
- Backport was done at r67745. https://bugs.ruby-lang.org/issues/14834#note-13
-
09:11 AM Bug #16675: Regression on Ripper in Ruby 2.7 when parsing new line
- For example,
```ruby
<<FOO.chomp
foo
FOO
```
Here-doc beginning token is just followed by its content and terminator. -
08:34 AM Revision f9f3510e (git): Hook an experimental alert from Actions
-
-
- As `String#split` with the default argument drops trailing newline
as a separator, preceding `String#chomp` is futile. -
-
- There needs to be more discussion on the behavior of this method.
Logically, `except_indices` should be the complement of `values_at`, so for the purpose of writing test cases I added this stopgap:
```ruby
def except_indices(*idx)
se... -
- In my opinion `omit_indices` is the best name in the thread so far, but I'm not a huge fan of making my methods verbs. I propose `arr.except_indices(1, 2, 3)` as an alternative.
The negation of `values_at()` is a semi-common occurrenc... -
04:49 AM Revision fcd60502 (git): Fix a typo
-
-
- `+1`. This is something I'd love to see implemented because this is actually the most common use case for me.
Could be implemented in a backwards compatible way (set `open_timeout` and `read_timeout` to `total_timeout` and abort appro...
03/06/2020
-
09:48 PM Bug #15608: What should be the correct output for Method#inspect with singleton methods?
- I rebased my patch against the current master branch and added a pull request for it: https://github.com/ruby/ruby/pull/2949
-
-
-
-
-
09:15 PM Bug #16675: Regression on Ripper in Ruby 2.7 when parsing new line
- > Ripper doesn't fire the events in the order of the source, typically around here-documents.
Can you explain issue with here-documents? AFAIK, having used Ripper for over a decade now, this is the first time we've identified Ripper fir... -
- lsegal (Loren Segal) wrote in #note-2:
> 4) Finally, comments have always been allowed to separate expressions, but this only broke as of 2.7.0. Ripper even all the way back in Ruby 2.3.3 was able to handle the "fluent dot" scenario jus... -
- Feel free to comment on this issue. But do not change the status of tracker's issue without the maintainer's decision.
-
- I'm not sure why this was closed so quickly. There is a real bug here affecting many users who indirectly rely on this core library.
It may be the case that comments can be placed between dots, but that should not affect parsing order... -
- This is because comment lines can be placed between fluent dot.
That means it is undecidable if a newline before a comment line is ignored until comment lines end. -
12:03 AM Bug #16675 (Closed): Regression on Ripper in Ruby 2.7 when parsing new line
- Hello
While using migrating RSpec documentation to last Yard. I noticed an issue in code parsing and Ripper. The regression appears on Ruby 2.7 and Head.
``` ruby
require 'pp'
require 'ripper'
SOURCE = "def name\n # comment\n... -
09:06 PM Revision f991340e (git): Document defined? and global_variables handling of regexp global variables [ci skip]
- Fixes [Bug #11304]
-
08:17 PM Misc #15893: open-uri: URI.open status
- Thank you. So I gather
`URI.open(url, **options)`
becomes
`URI(url).open(**options)`
(Re the deprecation of old Ruby versions: users of gems often want to use them with whatever is on their OS, and that currently means we re... -
06:00 AM Misc #15893: open-uri: URI.open status
- cabo (Carsten Bormann) wrote in #note-3:
> So what is code that needs to be portable to older Rubies supposed to call now? `URI.open` only works since 2.5. We need to support 2.3 and 2.4 as well.
> ...
You can use URI#open.
```
%... -
- So what is code that needs to be portable to older Rubies supposed to call now? `URI.open` only works since 2.5. We need to support 2.3 and 2.4 as well.
`OpenURI.open_uri` ?
-
07:08 PM Bug #16676 (Closed): `#hash` can change Hash object from ar_table to st_table
- 4c019f5a626523e99e2827ed917802e3097c380d
c3584dfacce4d0f2058d8403de6fdce4fd4d686b -
- # Points
* Hash representation `ar_table` has a problem from Ruby 2.6 (need to backport)
# Problem
From Ruby 2.6 `Hash` object is represented by `ar_table` (for small (<=8) pairs) and `st_table`.
To lookup hash table, `Object#h... -
- RHASH_AR_TABLE_SIZE() has assertion that it is a ar_talbe.
The last commit breaks this assumption so check ar_table first. -
- ar_table can be converted to st_table just after `ar_do_hash()`
function which calls `#hash` method. We need to check
the representation to detect this mutation.
[Bug #16676] - 05:39 PM Revision 44462d32 (git): * 2020-03-07 [ci skip]
-
-
-
12:41 PM Revision 0256e4f0 (git): thread_pthread.c: allocate sigaltstack before pthread_create
- A new (not-initialized-yet) pthread attempts to allocate sigaltstack by
using xmalloc. It may cause GC, but because the thread is not
initialized yet, ruby_native_thread_p() returns false, which leads to
"[FATAL] failed to allocate memo... -
11:55 AM Revision baaf6815 (git): Improve docs for Prime.{prime_division,int_from_prime_division} (#8)
- Move explanation for the decomposition array from the Example section
to the method description. Mention the term "multiplicity".
Use examples that also demonstrate factors with multiplicity
other than 1, and avoid factors/multiplicitie... -
- https://github.com/ruby/prime/commit/549c1b86f1
-
- https://github.com/ruby/prime/commit/230a5af325
-
- Previously, it would be an infinite loop if passed a non-prime
integer.
Also, Prime.include? should also provide similar results to
Module#include? if passed a Module, so handle that.
For consistency with Enumerable#include?, return fa... -
06:50 AM Feature #16615: Group style access scope for macros
- shevegen (Robert A. Heiler) wrote in #note-1:
> Two comments from me in regards to the proposal:
> ...
The `attr_*` family of methods currently enjoys special treatment here, as they are the only methods
which define instance methods ... -
- See https://rubyci.org/logs/rubyci.s3.amazonaws.com/freebsd12/ruby-master/log/20200306T043002Z.fail.html.gz
-
12:09 AM Bug #16383: TracePoint does not report calls to attribute reader methods
- > On microbenchmark, it is 30% slower, so we need to invent a hack to support it.
In JRuby, that hack is called the `--debug` flag, which enables the full set of traces. At some point CRuby's probably going to have to do something sim...
03/05/2020
- 10:49 PM Revision 2630757f (git): * 2020-03-06 [ci skip]
-
-
- Are there plans to implement this in master, any timeline?
Andy Maleh wants to add specs for this in https://github.com/ruby/spec/pull/761 which is nice but we would need an expected fix version. -
01:59 PM Bug #16672: net/http leaves original content-length header intact after inflating response
- jeremyevans0 (Jeremy Evans) wrote in #note-8:
> `total_out` doesn't give you the full size of the output until after the input is fully processed. So if there is an exception or other early exit from the block passed to `inflater` befo... -
- jmreid (Justin Reid) wrote in #note-7:
> > Modifying the Content-Length header is tricky because you do not know the decoded size until after decoding
> ...
`total_out` doesn't give you the full size of the output until after the input... -
- jeremyevans0 (Jeremy Evans) wrote in #note-6:
> I don't think net/http should be modifying the response headers. I think the response headers should remain exactly as sent by the server.
I do agree in general. However, in this case net/... -
- jmreid (Justin Reid) wrote in #note-5:
> > So the method appears to be operating exactly as documented.
> ...
I think I understand your reasoning better now. net/http is currently deleting the `Content-Encoding` header, so deleting or... -
- > So the method appears to be operating exactly as documented.
I'm not saying that method isn't working as intended. It's working as intended and I'm just using it to show the size of the header for the request net/http made. My comment... -
- jmreid (Justin Reid) wrote in #note-3:
> The issue here is that this ` "content-length"=>["2733"]` value is 2733. The `res.body` at this point is 9995, so `content-length` needs to match that or not exist. Otherwise it causes browsers t... -
- ioquatix (Samuel Williams) wrote in #note-2:
> Are you using `res.content_length`? Why can't you just use `res.body.to_s.bytesize`?
`res.content_length` is just the `content-length` response header from the net/http request:
```
... -
- openbsd current seems to behave the same as other OSs.
https://rubyci.org/logs/rubyci.s3.amazonaws.com/openbsd-current/ruby-master/log/20200305T063005Z.fail.html.gz -
-
- The current master branch and 2.7, 2.6 and 2.5 couldn't build with FreeBSD 12
see https://github.com/rbenv/ruby-build/issues/1272#issuecomment-455836665
We can build with `--disable-dtrace` flag on FreeBSD 12. -
-
- ```
warning C4117: macro name '_INTEGRAL_MAX_BITS' is reserved, '#define' ignored
``` - 02:31 AM Revision 74051183 (git): * 2020-03-05 [ci skip]
-
-
- I'm not against this issue but for record: commit 8a72c77c7920d129818b7b83bb4fa669cd7e3f7d says "as requested by devs, support for BASERUBY prior to 2.1". and the "devs" here included ko1. At that time his machine was a Panasonic laptop...
-
12:16 AM Feature #16673 (Open): total_timeout for Net::HTTP
- `Net::HTTP` allows setting `open_timeout` and `read_timeout`, but sometimes I just want to make sure an API call will finish within a set amount of time, and am not concerned with how long opening the connection takes and reading the con...
03/04/2020
-
11:42 PM Bug #16660: Struct#deconstruct_keys inconsistent behavior
- (For some reason cannot edit the original post).
> Prior to that change an empty hash was returned in both cases.
I think, the less confusing behavior would be to ignore the unknown keys without "failing fast" (i.e., returning an empt... -
10:25 PM Bug #16672: net/http leaves original content-length header intact after inflating response
- Are you using `res.content_length`? Why can't you just use `res.body.to_s.bytesize`?
-
- When using net/http to make a request to a resource, the default request headers are the following (when you have ZLIB available):
`"accept-encoding"=>["gzip;q=1.0,deflate;q=0.6,identity;q=0.3"], "accept"=>["*/*"], "user-agent"=>["Ruby"... -
-
-
-
12:43 PM Feature #16670: Reverse order of `expression` in `pattern` for 1-line pattern matching while it's still experimental
- I think it's important to realize that it's the goal of pattern matching to be similar to data constructors. It proved itself to be a good solution in the long run, this is why languages mentioned above chose this approach. Of course, I'...
-
- The pattern syntax looks very close to hash literals, but its semantics is quite different.
So I think it is very hard to distinguish them without a preceding mark (`in` keyword for now). -
-
-
- naruse (Yui NARUSE) wrote in #note-2:
> Through the discussion around CI, I reached a conclusion "Runtime environment and development environment are different".
Note that it is true for years, for instance, Windows 9x was supported ... -
08:24 AM Misc #16671: BASERUBY version policy
- Through the discussion around CI, I reached a conclusion "Runtime environment and development environment are different".
Though CentOS and macOS bundles very old ruby, but it's no problem because they are just runtime environment.
I... -
- Ruby 2.7 (MRI) requires Ruby 2.2 or later (== BASERUBY) to build from repository.
Tarball does not need any installed Ruby.
To build latest Ruby from repository, you need to build Ruby 2.2 and later from a tarball.
Can we make the B... -
-
-
- This reverts commit 87f6154bb4c67ca77ee353bb1fe25a922036c0e5.
It turned out that the change fails to build on macOS
https://rubyci.org/logs/rubyci.s3.amazonaws.com/osx1014/ruby-master/log/20200304T074503Z.fail.html.gz
```
+ make 'TESTS... -
- This reverts commit efd641ffab34e433a8d8a7d78914576f2425aa90.
This changeset seems to be needed to suppress a warning on Ubuntu 20.04
https://rubyci.org/logs/rubyci.s3.amazonaws.com/ubuntu/ruby-master/log/20200304T033004Z.log.html.gz
``... -
-
- Starting GCC 7, warnings about uninitialized variables are issued around
them. Such warnings could be false positives (all versions of clang do
not warn), but adding initializers there could never be bad things. -
- There is a test directory named test/-ext-. Because this directry
starts with a hyphen, we have to cheat test/unit in order for it to
run the tests underneath. TESTS='-- -ext' worked for a long time.
Let's not break that maneuver. -
- See also
35eb12c06397e770392a41343cbffc4b204e15c9
6f5eb285077d9abf8f97056531996c58674b570c
687308cf0dab0af675e40da2b6ab8ccd5f77c072
b6a2d63eb3dbc31e110e8cb95e054dd71d49a611 -
- rb_transient_heap_managed_ptr_p is available only when USE_TRANSIENT_HEAP.
Need #if guards. -
-
-
- GC.latest_gc_info[:major_by] can return `oldmalloc` because of
last GC status. -
- `GC.start(full_mark: false)` can run full GC because of last
GC status. Just after major GC, the possibility to run major GC
next time is too small (not a zero, but too small possibility). -
- Call GC.verify_internal_consistency only for Gem related test
on i386-solaris. -
-
-
03/03/2020
-
- Thanks for your response!
I realised it didn't affect the build, but for me a proper configure is showcasing the quality of a package.
Whenever I am confronted with sloppy configuration I am doubting the quality of everything else. -
- I was able to reproduce this by building from the 2.6.5 tarball, and making `ruby` be ruby 1.8.7, without any use of `--with-baseruby`. The tarball automatically sets `BASERUBY` based on `ruby` even though it isn't needed in most tarbal...
-
- Thanks for the info, though I am wondering, why configure doesn't take care of that automatically.
Isn't this a tarball what I get by downloading via https://cache.ruby-lang.org/pub/ruby/2.6/ruby-2.6.5.tar.gz? -
- Build from a tarball, or configure with `--with-baseruby=no` option.
-
- Yes, ruby -v:
ruby 1.8.1 (2003-12-25) [i386-linux-gnu]
which ruby:
/usr/bin/ruby
Extract from my log file:
```
BASERUBY = /usr/bin/ruby
CC = gcc
LD = ld
LDSHARED = gcc -shared
CFLAGS = -O3 -ggdb3 -Wall -Wdeclaration-after-stateme... -
- Probably you use ruby 1.9 or earlier as `BASERUBY`, right?
-
08:17 PM Feature #15605: json library needs more frequent releases
- > I tried to make a step in that direction 2 weeks ago
Thanks for the link, I had no idea. I suppose I'll subscribe there and wait.
-
- I tried to make a step in that direction 2 weeks ago in https://github.com/flori/json/pull/402#issuecomment-586585888
But no answer yet from flori (even on such a trivial PR).
The current maintainer doesn't answer frequently enough for ... -
-
-
-
04:49 PM Feature #16670: Reverse order of `expression` in `pattern` for 1-line pattern matching while it's still experimental
- ....and also, one more example, now just in Ruby:
```ruby
# that's what we always had:
a, b = [1, 2, 3]
# could be pretty complicated:
a, (b, c), *d = [1, [2, 3], 4, 5]
# ...but now let's imagine we need to unpack a simple Hash... -
- For the record, both Haskell and OCaml have let expressions. And yes, both have patterns on the left side, just like in F# or Rust.
-
- In favor of the proposal, standalone match looks this way in other languages:
```
# Rust:
let (x, y, z) = (1, 2, 3);
# Erlang:
{X, Y} = {1, 2}.
# Elixir:
{a, b, c} = {:hello, "world", 42}
# F#:
let {First=first} = alice
# Swi... -
- I do not think reddit discussions are that useful, largely because it is difficult to find
what is really going on (content-to-noise ratio), and the article title was actually
"2.7's pattern matching official docs (recently merged)". z... -
03:14 PM Feature #16670 (Closed): Reverse order of `expression` in `pattern` for 1-line pattern matching while it's still experimental
- Currently the 1-line syntax for pattern matching is:
```
# Usage: <expression> in <pattern>
expression = {
pattern: "Example"
}
expression in {pattern: something}
# something => "Example"
```
Is it technically possible... -
03:40 PM Feature #16667: Allow parameters to Symbol#to_proc and Method#to_proc
- Hanmac (Hans Mackowiak) wrote in #note-8:
> @jgomo3 i found my old Symbol#call code
> ...
Great helper.
Well, that is another way.
So yes, the whole point of this ticket is to propose to allow that kind of expressions.
In other words,... -
02:27 PM Feature #16667: Allow parameters to Symbol#to_proc and Method#to_proc
- @jgomo3 i found my old Symbol#call code
~~~ ruby
class Symbol
class SymbolHelper
def initialize(obj,methId,*args)
@obj= obj
@args=args
@methId=methId
end
def method_missing(methId,*args)
... -
- Hanmac (Hans Mackowiak) wrote in #note-5:
> i tried `ary.map.with_object(:id,&:dig)` but it just returned `:id`
> ...
Amazing this approach.
Sadly, it will work only for Arity-1 functions.
If you want to dig more, how to do it? e.g, su... -
- sawa (Tsuyoshi Sawada) wrote in #note-4:
> I already know that. That does not make `ary.map(:dig.to_proc(:id))` work. You seemed to have missed my point.
Ok, it would be actually `ary.map(&:dig.to_proc(:id))`.
But that is not the impor... -
- i tried `ary.map.with_object(:id,&:dig)` but it just returned `:id`
but this one would work: `ary.each_with_object(:id).map(&:dig)` -
- jgomo3 (Jesús Gómez) wrote in #note-3:
> The idea is to extend **to_proc** so it creates a **Proc** that calls the method on the given object using as arguments the parameters set in **to_proc** call.
> ...
I already know that. That do... - 03:11 PM Revision 14dd377e (git): * 2020-03-04 [ci skip]
-
-
-
-
- Great report.
-
11:07 AM Bug #16669: Rails Action Text unit tests fail since b9007b6c548f91e88fd3f2ffa23de740431fa969
- Thanks for the information. I was aware it reproduces with Action View also but unable to create some smaller steps to reproduce. Let me try to provide some smaller test cases with Action View.
-
10:45 AM Bug #16669: Rails Action Text unit tests fail since b9007b6c548f91e88fd3f2ffa23de740431fa969
- Action Text has much dependencies, and the failure is hard to understand which line is the cause of failure since that result show no stacktrace.
Action View failure is more ease to understand which line is the cause of failure.
http... -
- This issue has been reported at Rails repository https://github.com/rails/rails/issues/38613
It always reproduces since https://github.com/ruby/ruby/commit/b9007b6c548f91e88fd3f2ffa23de740431fa969
but I do not know how to create minim... -
- As the headings become link anchors, remove less useful notes.
[ci skip] -
-
- Check heap consistency after each test to debug.
https://rubyci.org/logs/rubyci.s3.amazonaws.com/unstable11x/ruby-master/log/20200303T012406Z.fail.html.gz -
-
05:43 AM Revision 91440ff1 (git): Convert incompatible encoding symbol names
03/02/2020
-
09:42 PM Feature #16665: Add an Array#except_index method
- Hello, I was part of this discussion on Railstalk and the Rails-core issue, you can peek for additional context here: https://github.com/rails/rails/pull/38611#issuecomment-593627540
It was closed on Rails-core and suggested to be pro... -
07:19 PM Feature #16665: Add an Array#except_index method
- sawa (Tsuyoshi Sawada) wrote in #note-2:
> For the positive counterpart, we have `Array#values_at`. I think the method name to be proposed should be somehow aligned with that.
May I ask you to check my answer to Robert A. Heiler? -
- shevegen (Robert A. Heiler) wrote in #note-1:
> I can not comment on how useful this may be; I think I may have added something similar
> ...
I also thought a lot about naming and have a few variants:
``` ruby
omit_indices
omit_in... -
09:01 AM Feature #16665: Add an Array#except_index method
- Isn't this easily solvable with `select` and `with_index`?
``` ruby
%w( a b c d e f).select.with_index{|l,index| index > 1 } # => ["c", "d", "e", "f"]
```
-
- > I am not sure how allowing parameters to Symbol#to_proc and Method#to_proc would make:
> ...
Currently, **to_proc** on symbols creates a **Proc** that receives an object and calls on it the method with name equal to the symbol.
The id... - 05:44 PM Revision 485ef0bd (git): * 2020-03-03 [ci skip]
-
- send() has special method launcher in VM and it has special
method_missing caller. This path doesn't set
ec->method_missing_reason which is used at exception creation,
so setup this information. Without this setting, NoMethodError
except... -
- something might be wrong with your ruby version, because `def self.detect(path, uplevel_limit: 0)` is valid ruby code
-
- ```
./tool/file2lastrev.rb:10:in `require': /home/imptst/ruby/ruby-2.6.5/tool/vcs.rb:127: syntax error (SyntaxError)
```
```ruby
def self.detect(path, uplevel_limit: 0)
```
Should be:
```ruby
def self.detect(path, uplevel_limit... -
-
-
-
-
-
- Explicit `name:` entry was requested by @nobu.
-
- This target can be a build matrix. Also it does not make sense to test
it on mjit. -
- One can specify working directory of a step, no by `cd foo` inside of
the run. See also
https://help.github.com/en/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsrun -
- The `branch:` specifier was necessary before, to prevent double-testing
master and trunk. Now that we no longer have trunk, we can slim the
expressions.
See also: https://help.github.com/en/actions/reference/workflow-syntax-for-github-... -
- They were necessary when developing YAMLs, but not useful any longer.
-
-
- It seems UBSAN is quite stable now.
-
- Darwin is no longer tested using Travis CI. See also commit
91aa8bfff8a9f9c0af96915c120d863fc474e8d5 -
-
- TestRelineAsReadline#test_insert_text expects Readline.point == 0
at the beginning of the test, but a test violate this assumption. -
- vm_cc_fill() fills CC information into stack allocated memory so
it is not cleared. So we need to clear CC->aux. -
- Some other tests can set Reline.completion_proc, so if it is nil,
simply skip this test. -
- This reverts commit 0bfee2397ba59112902d2b49f08461db3a637b46.
-
- 02:44 AM Revision 5d3b38d6 (git): * 2020-03-02 [ci skip]
-
- https://gist.github.com/ko1/a71f7cbcfbd61ba004bffdfedab9f5f2#file-brlog-trunk-random0-20200302-020213-L2127
03/01/2020
-
-
- > Does anyone else think the same syntax would be beneficial for Strings?
I do not doubt that it can be useful. One advantage of your proposal is that it
is very short and succinct.
Personally, though, I prefer .gsub() or .gsub!()... -
- For removing a set of characters, there is already `String#delete`. And for your other cases, there is a similar proposal https://bugs.ruby-lang.org/issues/12698.
-
- I think this or something similar was suggested in the past, even aside from
the two linked in proposals. So this may even be older than 5 years. :)
I do not remember what the conclusion was in all these proposals (and perhaps
I mis... -
- I am not sure how allowing parameters to `Symbol#to_proc` and `Method#to_proc` would make:
```ruby
ary.map(:dig.to_proc(:id))
```
possible as `Array#map` does not take an argument. What do you want it to return?
Needless to say, it i... -
- Allow parameters to Symbol#to_proc and Method#to_proc
So we can say:
``` ruby
ary.map(:dig.to_proc(:id))
```
Instead of
``` ruby
ary.map { |e| e.dig(:id) }
```
Oppening the posibilities to refine the `&` operator i... -
- For the positive counterpart, we have `Array#values_at`. I think the method name to be proposed should be somehow aligned with that.
-
05:35 AM Revision d25a4f41 (git): Allow trailing comma in hash pattern