Activity
From 07/04/2019 to 07/10/2019
07/10/2019
-
07:41 PM Bug #15993 (Open): 'require' doesn't work if there are Cyrillic chars in the path to Ruby dir
- I’m trying to build a cross-platform portable application with Ruby onboard and there is a problem on Windows.
A user usually installs it to the Roaming folder which sits inside a user folder which can often have not a Latin name or co... - 06:37 PM Revision d57ce99b (git): * 2019-07-11
-
05:03 PM Bug #15986: `TestJIT#test_block_handler_with_possible_frame_omitted_inlining` fails on s390x and armv7hl
- So this is my hacked up test case:
~~~
$ git diff
diff --git a/test/ruby/test_jit.rb b/test/ruby/test_jit.rb
index 08494cbbbb..9ace7754d4 100644
--- a/test/ruby/test_jit.rb
+++ b/test/ruby/test_jit.rb
@@ -944,9 +944,15 @@ def as... -
04:12 PM Revision 12762b76 (git): Don't manipulate GC flags directly
- We need to disable the GC around compaction (for now) because object id
book keeping can cause malloc to happen and that can trigger GC. -
09:27 AM Feature #10463: :~@ and :!@ are not parsed correctly
- Interesting - I did not know this. sawa finds stuff. :)
Personally I would be in favour of changing the behaviour as Jeremy described (I also think this
may be a bug or perhaps an oddity), but I guess it depends on a) whether matz wa... -
09:15 AM Bug #15992 (Closed): An exception breaks monitor state and cause deadlock
- Applied in changeset commit:git|f91879a7b548284c93743168acfd11e3d2aeefac.
----------
handle_interrupt to defend monitor state [Bug #15992]
If an exception is raised from another thread for example Timeout
and this thread is just after ... -
- lib/monitor.rb provides Monitor.
But its state handling is weak for interrupts caused by Thread.kill for example timeout libraries.
Timeout exception may happen everywhere. If it raised when the thread is executing
```ruby
def ... -
- If an exception is raised from another thread for example Timeout
and this thread is just after `mon_exit`'s `@mon_owner = nil`,
the exception breaks the state of MonitorMixin. To prevent that situation,
it need to block interruption in ... -
04:48 AM Misc #15930: DevelopersMeeting20190711Japan
- * [Bug #10463] :~@ and :!@ are not parsed correctly (jeremyevans0)
* Can we deprecate the automatic conversion of `~@` to `~` and `!@` to `!` in method names and symbols? -
04:33 AM Misc #15930: DevelopersMeeting20190711Japan
- * [Feature #15865] `<expr> in <pattern>` expression (mame)
* We have some opinions: scoping, matching strictness, the keyword `in`, and the word order. But all are not specific to the one-line matching. I think it is acceptable if `... -
-
- I agree this is a bug. I am not sure if it is a documentation bug or code bug. The existing documentation for `Array#pack` does suggest the count should specify output bytes (`width of the resulting field`), while the `m` count current...
-
- I agree this is a bug. This has been broken since the code was originally added in commit:18c0a86cc680929bbd8c48f4f45a197e3e68c70a. I added a pull request upstream to fix it: https://github.com/ruby/fileutils/pull/36
-
03:33 AM Revision 1d2ec4b2 (git): Added Etc::VERSION
-
07/09/2019
-
11:18 PM Feature #15991: Allow questionmarks in variable names
- shevegen (Robert A. Heiler) wrote:
> I do not see why this would make the design more "coherent", per se.
I guess "design coherence" is a very subjective notion \^\^"
What I meant by that is that in most cases in Ruby, whether an i... -
06:53 AM Feature #15991: Allow questionmarks in variable names
- I personally often write code like this:
```ruby
class Foobar
attr_reader :completed
def completed?
@completed
end
end
```
This feels unnecessary complex to me. In #12046 it was discussed to allow `attr_reader :... -
- I couldn't find an existing proposal for a local variable that ends with `?`. There are many proposals for "attr_reader :foo?" (#5781 #10720 #11167 #12046), but all the tickets have been rejected. (#5781 is still open, but I guess it i...
-
07:57 PM Feature #15897: `it` as a default block parameter
- As a user of both Kotlin and RSpec, here's my 0.01 cents: I've been using Kotlin for almost 1.5 years, and the implicit `it` is really nice shortcut, without making the code too harder to understand. Even newcomers seem to get `it` prett...
-
02:53 PM Feature #15897: `it` as a default block parameter
- I think we should listen to RSpec users here like @joallard and would welcome more users to reply on this thread.
People who maintain software defining `it` probably have a different view than their users.
If RSpec users understand `it... -
- JonRowe (Jon Rowe) wrote:
> its a "this shadows the most commonly used method in the most downloaded rubygem"[1], its not one or two people this will affect.
It only "shadows" (by that I understand "no longer works in that case") for... -
11:06 AM Feature #15897: `it` as a default block parameter
- @mame I did, I apologise for not making it clear, I'm reiterating it to add weight to the con, its not just a simple "it is somewhat fragile, it may refer to a wrong variable" its a "this shadows the most commonly used method in the most...
-
06:34 PM Feature #15899: String#before and String#after
- I'd like to add my +1 to this idea. Splitting a string by a substring (and only caring about the first result) is a use case I run into all the time. In fact, the example given by @kke of splitting a `Content-Type` HTTP header by the sem...
-
-
-
-
- nobu (Nobuyoshi Nakada) wrote:
> jeremyevans0 (Jeremy Evans) wrote:
> ...
Well, `foo.!@` would be a syntax error with the patch. Is there a reason other than backwards compatibility to keep this automatic aliasing of `!@` to `!` and `... -
- jeremyevans0 (Jeremy Evans) wrote:
> nobu (Nobuyoshi Nakada) wrote:
> ...
Sorry, forgot `@`, I wanted to mean `!foo` and `foo.!@`. -
- nobu (Nobuyoshi Nakada) wrote:
> If `:!@` and `:!` are different things, also `!foo` and `foo.!` are different things.
I don't believe that is true. With the above patch:
```ruby
class A
def !; :! end
def ~; :~ end
end
... -
- If `:!@` and `:!` are different things, also `!foo` and `foo.!` are different things.
This means a backward incompatibility. -
- I did some research, and this is related to the fact that Ruby allows `!@` and `~@` as method names (back to the initial SVN revision for `~@`), silently dropping the `@` from the method name:
```ruby
class A
def !@; :!@ end
de... -
-
- FYI: RubyCI platforms include [RHEL 7.1 s390x][1] and [Ubuntu armv8 (aarch64)][2], and their results are both green at the present time. So the cause would be the other factor than CPU, I guess.
[1]: https://rubyci.org/logs/rubyci.s3... -
02:40 PM Bug #15986 (Feedback): `TestJIT#test_block_handler_with_possible_frame_omitted_inlining` fails on s390x and armv7hl
- I see. Thanks for the information. At this moment I cannot do anything either, so I'll wait for you to collect the information from the CI system somehow.
-
- I wish this was easier to debug. The problem is that this is test failure and it happens on build system, where I don't have access. Trying to reproduce it on my system, this does not work:
~~~
$ echo "
def multiply(a, b)
a *= b
... -
- This `last_state` is set to `lex.state` just before the `switch`
statement, and `token_flush` nor `nextc` never change the state. - 03:09 PM Revision 57b8ca21 (git): * 2019-07-10
-
- alanwu (Alan Wu) wrote:
> `Kernel#lambda` is in a weird spot. Even though it's a method, making it behave like one has the unfortunate side-effect of allowing proc transformation.
Yes, the semantics of `Kernel#lambda` have always bee... -
02:32 PM Feature #15973: Let Kernel#lambda always return a lambda
- > Can I ask you why you need this feature?
I want to be able to forward a block to `Kernel#lambda`.
`Kernel#lambda` is in a weird spot. Even though it's a method, making it behave like one has the unfortunate side-effect of allowi... -
- It should be OK when passing the buffer from callers, but doesn't work with a library which returns a buffer allocated inside.
FYI: you can allocate the buffer by `rb_str_new(NULL, size_you_want)` at once. -
- Instead of working on a separate buffer then asking Ruby to take ownership, you could make changes to the buffer of a string:
```c
VALUE new_string = rb_str_new("", 0);
rb_str_resize(new_string, size_you_want);
do_work(RSTRING_PTR(... -
-
-
12:16 PM Revision 9f275f79 (git): Restore support library for only test files that are digest and csv.
-
-
06:55 AM Bug #15832 (Closed): IPAddr.new accepts invalid mask IP address
- I merged it.
-
-
-
- This was fixed between Ruby 2.2 and 2.3:
```
$ irb22
irb(main):001:0> def !; end
=> :!
irb(main):002:0> !
/usr/local/lib/ruby/2.2/irb/input-method.rb:151:in `gets': private method `!' called for false:FalseClass (NoMethodError)
... -
-
- `system` was made more strict for redirection errors between Ruby 2.2 and 2.3:
```
speedstar$ ruby22 -e "p system('true', out: %w(bad/file.txt w))"
nil
speedstar$ ruby23 -e "p system('true', out: %w(bad/file.txt w))"
-e:1:in `s... -
-
-
-
04:01 AM Revision 515e106f (git): [DOC] Add link to Enumerable#grep from Enumerable#select
-
-
- This was fixed between 2.1 and 2.2:
```
$ ruby21 -ruri -e "p URI 'http://localhost:3000/?url=google.com&clipRect={"top":0,"left":0,"width":1050,"height":700}'"
/usr/local/lib/ruby/2.1/uri/common.rb:176:in `split': bad URI(is not... -
- I believe this issue was fixed by commit:aa107497cd379b713eba8cecdb9a882bb1e0dd89, which removed the `argc` and `argv` variables in favor of using `rb_execarg_commandline(eargp, &prog)`, and `eargp` and `prog` are always initialized.
-
-
- This issue was fixed between Ruby 2.2 and 2.3:
```
$ ruby23 test.rb
User
$ ruby22 test.rb
.../user.rb:4:in `yield': fiber called across stack rewinding barrier (FiberError)
from .../user.rb:4:in `<top (required)>'
... -
- ruby-doc.org is a third party site, so this would be an issue to report to them. However, `%xdate` no longer appears on the linked page.
-
- I don't think this is a bug, the current behavior is consistent and what I would expect. It would be inconsistent to assume the current year for `%m/%d` format in some cases and not in others. It is better to raise an exception if that...
07/08/2019
- 11:39 PM Revision 9b18cb34 (git): * 2019-07-09
-
- @JonRowe Thank you for your opinion, but I'd be happy if you could read my original proposal carefully. I've already pointed out the issue (and said my opinion against the issue).
> Cons:
> ...
I hear from some people that they are ... -
- Its worth pointing out that this would always have to be lower priority than methods and other such locals defined in order to allow code to work. If precedence for this was changed to later override existing definitions of it, or simply...
-
-
- > I thought such an issue would've already been discussed but no number of searches
> ...
I think this has been discussed before - I can not point to another issue request for this,
though, so perhaps I misremember. I also don't rememb... -
10:13 AM Feature #15991: Allow questionmarks in variable names
- If this proposal will not cause some serious conflicts, it seems to be also useful for those cases:
```ruby
class Task
def initiailize(name, ready)
@name, @ready = name, ready
end
attr_reader :name
def ready?
... -
- Hi,
I thought such an issue would've already been discussed but no number of searches allowed me to find a similar request. Feel free to close if I missed a previous refusal.
From time to time, especially when trying to clear up co... -
01:49 PM Feature #15973: Let Kernel#lambda always return a lambda
- "It's already broken, why not break it more" is not what I can follow.
Can I ask you why you need this feature? If this not more than a matter of consistency, I would like to second @eregon's proposal: lambdas without literal blocks ... -
- I would also like to note that if we revert back to the behavior in 2.4, code that relied on `lambda` without block will not have an easy upgrade path.
```ruby
def make_a_lambda
lambda
end
```
is not equivalent to
```rub... -
- The 2.4 spec is a bit problematic since it makes it impossible to forward a
block to `Kernel#lambda` with a block pass. In the rest of the language
forwarding a block has no effect on semantics compared to passing one
literally. The i... -
-
10:02 AM Feature #5735 (Closed): Extending the use of splat operator to when it is inside a hash
-
09:53 AM Feature #5735: Extending the use of splat operator to when it is inside a hash
- A similar feature has already been realized as the double splat operator. Please close this issue.
-
09:16 AM Bug #15989: irb-1.1.0.pre.1 crashes on using arrow up, home and delete
- I can reproduce (by hitting del at the end of the line). The cause is in the snippet below.
``` ruby
Reline::Unicode.get_next_mbchar_size('')
# => nil
```
`get_next_mbchar_size()` doesn't always return a number.
According to ... -
-
- 07:00 AM Revision 93c9405e (git): * expand tabs.
-
-
-
04:30 AM Revision 612cad5d (git): Let struct dump_config in objspace fit in a single cache line
- Let dump_config boolean members roots and full_heap be bit flags
instead
Closes: https://github.com/ruby/ruby/pull/2274 -
- I tried the last two gists with many Ruby versions (1.9-2.7) and could not produce a crash. These were compiled with clang 7 on OpenBSD. It's possible with a different compiler and compiler options the results would be different. Can ...
-
-
- `cmp_failed` was removed in Ruby 2.3.
-
-
- anatolik (Anatol Pomozov) wrote:
> Could anyone explain what this change tries to do?
It tries to separate the `-I` cflags from the non `-I` ones, as they are stored in different global variables. In general it probably doesn't caus... -
- sawa (Tsuyoshi Sawada) wrote:
> Can someone answer my question in https://bugs.ruby-lang.org/issues/14183#note-68? Perhaps @mame knows? If it is not decisive yet, that is fine. I just want to know what the developers have in mind at thi... -
- Can someone answer my question in https://bugs.ruby-lang.org/issues/14183#note-68? Perhaps @mame knows? If it is not decisive yet, that is fine. I just want to know what the developers have in mind at this point.
-
- It looks like `WEBrick::HTTPResponse#to_s` is currently broken anyway (https://github.com/ruby/webrick/pull/20). I agree that it makes sense to remove the method, and added a pull request to do so (https://github.com/ruby/webrick/pull/22).
-
01:59 AM Bug #10928 (Closed): optparse Switch#summarize code doesn't reflect its documentation
- Applied in changeset commit:git|3fcffceafd2bce7186851bf4899484c545a9ace8.
----------
Fix default argument values for OptParse::Switch#summarize
The documentation describes these arguments being hashes, and the method
is called with has... -
- Thank you, I've missed it.
Commit it please. - 01:59 AM Revision a2e0aaea (git): * 2019-07-08
-
- I'm not sure I would consider this a bug, but it seems like a reasonable change. Attached is an updated patch that applies against master.
-
- I don't think this is a bug. If Apache doesn't pass the `X-Forwarded-Proto` header, and the `X-Forwarded-Host` header doesn't include the port, then how would Webrick know that the request was originally submitted via https? I'm not su...
-
- This was fixed between 2.6 and 2.7.0-preview1:
```
$ ruby26 a.rb
in b
true
$ ruby27 a.rb
true
``` -
- From testing, this issue was resolved between Ruby 2.4 and 2.5.
2.4 output:
```
c_return -e:3 enable
line -e:5
c_call -e:5 method_added
c_return -e:5 method_added
line -e:8
... -
-
- This was apparently fixed between Ruby 2.3 and 2.4:
```
$ ruby23 -e 'p("<".force_encoding("UTF-8") =~ /[[:punct:]]/)'
nil
$ ruby24 -e 'p("<".force_encoding("UTF-8") =~ /[[:punct:]]/)'
0
```
-
-
- I think this is a bug and it should be fixed. Attached is a patch that fixes the issue by checking if the receiver is already a singleton class, and if so, calling `rb_singleton_class` to force the creation of the singleton class of the...
07/07/2019
-
- This appears to be a bug in the ffi gem, see https://github.com/ffi/ffi/issues/337.
-
- Considering `String#b` has now been present since Ruby 2.0, and renaming it would break tons of code, I think there is no chance of it being renamed. It looks like Radix has adjusted to it and works with `String#b` being defined by defa...
-
09:04 PM Feature #15897: `it` as a default block parameter
- Eregon (Benoit Daloze) wrote:
> I think this ambiguity is fairly intuitive and easy to resolve:
> ...
I would echo Benoit's comments here. As an avid RSpec user, I employ `it "does something"` without a block fairly often for prototyp... -
- I agree that this is a bug and it should be fixed. You can trigger it by calling `OptionParser::Switch#summarize` without arguments:
```ruby
require 'optparse'
o = OptionParser.new
o.on('-c'){}
o.instance_variable_get(:@stack)[2]... -
- The documentation describes these arguments being hashes, and the method
is called with hashes, so a hash default makes more sense.
The method would fail previously if called without arguments and @short
or @long contained a non-integer... -
-
- It appears this was fixed between ruby 2.3 and 2.4:
```
$ ruby24 /home/jeremy/Downloads/zlib.rb
62780
generating len=1000000000 string...
string length=1000000000
compressing...
^CINT
decompressing...
true
$ ruby23 /home/... -
- The `ng_assoc19.rb` and `ng_assoc19_strvalue.rb` examples are no longer syntax errors, so I think this can be closed.
-
-
-
- Class variable lookup just ignores singleton classes currently.
I assume this is intentional behavior so one can use the same variable in singleton methods (when defined under `class<<self`) and instance methods. -
- This issue is not specific to opening a singleton class (`class <<`), but applies to any case where the class being opened is a singleton class. You get the same output for:
```ruby
module Mod1
O = Object.new.singleton_class
c... -
- Get rid of unknown escape sequence warning, as `#` is not a
special character in C.
```
version.c:126:26: warning: unknown escape sequence '\#' [-Wunknown-escape-sequence]
fputs("last_commit=" RUBY_LAST_COMMIT_TITLE, stdout);
... -
09:33 AM Revision 68e58040 (git): Add coroutine context switch for i386-mingw32
- It's essentially a translation of Context.asm from Intel
to AT&T syntax. -
-
- Applied in changeset commit:git|d548073f68ae719933c328686df224f74a60d366.
----------
Enable indentation warning against `if` just after `else`
```ruby
if false
puts 'false'
else if true
puts 'true'
end # -:5: warning: mismatched in... -
- Warning only after a syntax error?
```
$ ./ruby -w
if false
else if true
end
-:3: syntax error, unexpected end-of-input, expecting `end'
-:3: `end' of `if' matched `else' before `if'
-:2: maybe `elsif'?
``` -
12:18 AM Feature #15990: "else if" causes confusing syntax error
The problem is that this is valid Ruby:
``` ruby
if false
puts 'false'
else if true
puts 'true'
end
end
```
So we can't really tell if `else if` is invalid until we parse the second `end`.
- 06:50 AM Revision a33948f4 (git): * 2019-07-07
-
- ```ruby
if false
puts 'false'
else if true
puts 'true'
end # -:5: warning: mismatched indentations at 'end' with 'if' at 3
end
```
[Feature #15990] -
-
-
- Fixed by commit:7be5169804ee0cfe1991903fa10c31f8bd6525bd.
-
-
- I don't think this is a bug. Killing a thread requires running ensure blocks until the thread exits, the ensure block for `ConditionVariable#wait` needs to reacquire the mutex. If it didn't, the method would exit with the mutex not loc...
-
-
-
- Looking at the mentioned commit, I'm not sure how it is possible that the commit broke it. The only code change is:
```diff
- http = klass.new(target_host, target_port)
+ http = proxy ? klass.new(target_host, target_port) : k...
07/06/2019
-
- @sawa Could you write a code example in the description? It would be very helpful to make the developer meeting efficiently.
```
p Integer("z", exception: false) #=> nil
p Integer("z", exception: nil) #=> excepted: nil, actual: i... -
- I agree for methods taking an :exception keyword argument.
I would consider this a bug to treat `nil` as "want exception".
Do you have examples of other methods taking a boolean option and treating `nil` the same as `true`?
Those sh... -
- * [Feature #15987] Let boolean option (such as `exception` in `Kernel#Complex`, `Kernel#Float`, `Kernel#Integer`, `Kernel#Rational`) be falsy vs. truthy
* Does this issue need matz approval or can it be fixed directly? If it does, doe... -
- josh.cheek (Josh Cheek) wrote:
> Why not a comment pragma for this, too? A flag seems out of place.
Thanks for your reply.
I think a pragma is pretty bad for changing the default value when there is no pragma, from the experience wi... -
- palkan (Vladimir Dementyev) wrote:
> I think, most gems won't use these features anyway: we, gem authors, need to support older versions;
Thanks for your reply. Agreed, I was thinking to that as well but did not mention it explictly.... -
- JonRowe (Jon Rowe) wrote:
> > FWIW, MSpec's it requires the description argument, so it cannot ever be ambiguous for the user.
> ...
I think this ambiguity is fairly intuitive and easy to resolve:
it's exactly the same rule as for met... -
- `$1` - `$N` (there can be more than 9 of them) are treated specially by the parser.
In fact, the only way they can work is special treatment by the parser, because there is potentially an infinite number of them.
And that's probably ... -
-
- I guess it should be possible to distinguish between "else if" and "elsif"
by the ruby parser already, since it does fail if the 'e ' part is there
in the first case, as otherwise the parser would accept the syntax. So I
think it woul... -
01:53 AM Feature #15990 (Closed): "else if" causes confusing syntax error
- ```ruby
if false
puts 'false'
else if true
puts 'true'
end
```
This fails with "syntax error: unexpected end-of-input, expecting end". `else if` isn't `elsif`, of course, but if a file contains `else if` (especially on one l... -
- I've noticed it and have a patch, but haven't committed it yet as not written the test using dummy timezone objects.
-
- Applied in changeset commit:git|f296c260ef3b2d1a9299dbb4a84df567972453f2.
----------
Fix segfault when using method reference operator without using result
Fixes [Bug #15985] -
- Seems fine.
-
- Fixes [Bug #15985]
-
-
07/05/2019
-
- Fixed by commit:01b3a3804334be19d013526d3edde2b84399ae43.
-
-
- I think this may be operating system/platform specific and could be fixed in a previous version. I could replicate the behavior on ruby 2.4.1p111 on x86_64-linux, but memory seemed to stablize around 180MB on ruby 2.7.0dev on i686-linux...
-
- Rubygems upstream merged the pull request, so this can be closed.
-
11:03 PM Bug #11214: Cannot Get Correct Binding from inside of C Method
- > I'm fairly sure having binding capture arguments passed to C methods is not possible.
TruffleRuby could do that! Sorry I know it's boasting and not relevant to MRI :) -
- I'm fairly sure having `binding` capture arguments passed to C methods is not possible. Ruby doesn't know the C function's parameter names at runtime. Even if that were possible, you wouldn't be able to handle cases where a C function t...
-
-
- I think this can be closed. It doesn't look like 2.3 actually shipped with `RubyVM::InstructionSequence.load` (disabled at commit:22ea03bb7e213d60e49a9cdd1ec1b221ef802e2a), and the equivalent code with `RubyVM::InstructionSequence.load_...
-
- 10:20 PM Revision 833cfeb2 (git): * 2019-07-06
-
10:19 PM Revision 89e178c7 (git): Fix showing document of ClassName.method_name in IRB
- In IRB, Time.new is split as "Time", ".", and "new". The receiver "Time"
is processed by #class method but it means that "Time" changes to
"Class". This commit fixes it. -
- I agree that this is a bug that should be fixed. The implementation automatically percent escapes invalid characters instead of rejecting them by design. However, I don't think that implies we should accept invalid percent escapes alrea...
-
-
-
- This was fixed between Ruby 2.2 and Ruby 2.3:
```
$ ruby23 -e "module M; end; class A; prepend M; end; class B<A; prepend M; end; p B.ancestors"
[M, B, M, A, Object, Kernel, BasicObject]
$ ruby22 -e "module M; end; class A; prepend... -
- The behavior seems even worse in the master branch and 2.7.0-preview1, with a RuntimeError without a calculation, and always false after a calculation:
```ruby
require 'tzinfo'
z = TZInfo::Timezone.get('Europe/Kiev')
t = Time.new(2... -
- Even funnier:
```ruby
winter = Time.new(2019, 12, 1, 14, 30, 12, z) # => 2019-12-01 14:30:12 +0200 -- offset is correct
winter.dst? # => true -- this is wrong!
(winter + 1).dst? ... -
- My current timezone is Europe/Kiev.
With default zone (how it was previously):
```ruby
summer = Time.new(2019, 6, 1, 14, 30, 12) # => 2019-06-01 14:30:12 +0300
summer.zone # => "EEST"
summer.dst? ... -
- All of the other similar regexp variables (`$& $' $+ $~ $(backquote)`) are listed by `global_variables`, so it would make sense for `$1` and similar to appear, or alternatively for the other 5 regexp globals not to appear if there is no ...
-
- This issue still exists in the master branch. Eric's patch no longer applies, but attached is a similar approach that works and includes a test. However, maybe there was a reason this wasn't committed originally?
-
04:40 PM Bug #15989: irb-1.1.0.pre.1 crashes on using arrow up, home and delete
- Adding a demo gif code
-
- When I do this:
1. Start irb
2. Define empty string `''`
3. Press arrow up
4. Press Home
5. Press Delete to remove first `'`
6. irb crashes
I get following exception:
```
33: from ../install/bin/irb:23:in `<main>'
32: f... -
-
12:38 PM Bug #15841: SegFault in OpenSSL::PKey::RSA#private_encrypt
- Both of PR is merged and this issue is resolved, so this can be closed.
- https://github.com/ruby/openssl/pull/255
- https://github.com/ruby/openssl/pull/258
Thanks! -
- It has unintentionally passed since 2.5.
-
- * [Feature #15631] Let round_capa for ID table not allocate excess capacity for power of 2 ints >= 4
* PR and further due diligence comments in https://github.com/ruby/ruby/pull/2278
- 10:01 AM Revision 0a2f598d (git): * 2019-07-05
-
-
- > Is that used in practice though? I know pending examples, but I would expect they at least have a description.
No but as Ruby doesn't allow method overloading you do create that ambiguity, and the possibility for future bugs due to ... -
06:23 AM Feature #15966: Introducing experimental features behind a flag, disabled by default
- > This is how frozen string literal support was introduced to Ruby (in addition to the per-file magic comment).
Why not a comment pragma for this, too? A flag seems out of place. A flag also sets it globally, preventing one from optin... -
- I don't have a huge preference either way, but this may be a design decision, so perhaps we
can ask matz either way; also in how strong the concept of "falsy" and "truthy" is in ruby.
I assume there were design considerations for when ... -
- The `exception` option in `Kernel#Complex`, `Kernel#Float`, `Kernel#Integer`, and `Kernel#Rational` distinguishes `false` vs. other values.
```ruby
Integer("z", exception: false) #=> nil
Integer("z", exception: nil) #>> ArgumentErro... -
- tk was removed in Ruby 2.4.
-
-
- This behavior hasn't changed since the initial report. However, it seems odd to just treat string subclasses (or strings with singleton classes) differently. Currently the behavior is to use C functions for (at least) String, Symbol, I...
-
- This was fixed in commit:965e9df38045594d126991e6a109c5746242d2ba.
-
-
- I don't think this is a significant issue with current Ruby, though it was certainly a bigger issue in previous versions. From some testing:
```
$ ruby22 -r active_record -e "t = Time.now; require 'English'; p(Time.now - t)"
0.004... -
- This was fixed between Ruby 2.3 and 2.4:
```
$ ruby23 -e '
> class C; def a() end end
> ...
nil
$ ruby24 -e '
> class C; def a() end end
> ...
#<UnboundMethod: C#a>
```
07/04/2019
-
- I think the attached patch should fix it. Passes `make check`. This is my first time working on the compiler though, so a more experienced committer should probably check the patch.
With the patch:
```
$ ruby --dump=insns -e 'ni... -
- I can reproduce this. Here's a backtrace:
```
Thread 1 received signal SIGSEGV, Segmentation fault.
0x000006441ce6cdcd in check_funcall_callable (ec=0x643ddd44e48, me=0x64472043dc0) at ./vm_eval.c:365
365 return rb_method... -
- I have a simple script that actually does nothing:
``` ruby
nil.:|;1
```
or
```ruby
:|.:!;:|
```
When I run it with `make run` for `miniruby` or I run it with the full built master.
I get a segmentation fault as follow... -
10:14 PM Feature #15966: Introducing experimental features behind a flag, disabled by default
- Eregon (Benoit Daloze) wrote:
> I expect gems wouldn't use it anyway because of the extra needed flag.
I think, most gems won't use these features anyway: we, gem authors, need to support older versions; it doesn't make a lot of sens... -
-
- > This generates a wrong output collection after doing this action.
Could you provide some examples and explain exactly what is wrong with the output collection? -
- I don't think ruby should disallow this via an exception. The use case
seems fairly odd, too - it is often more idiomatic to do .map, .select,
.reject etc... -
09:38 AM Bug #15984: deleting from a collection while iterating on it
- that totally depends on how you interate over the collection.
if you do it right, ruby has no problem with that -
07:58 AM Bug #15984 (Closed): deleting from a collection while iterating on it
- If you tried to delete from a collection while iterating on it Ruby will allow you to do this flawlessly. This generates a wrong output collection after doing this action. An exception should be thrown to disallow this to be done.
-
- JonRowe (Jon Rowe) wrote:
> it # creates a pending example with no implementation
Is that used in practice though? I know pending examples, but I would expect they at least have a description.
FWIW, MSpec's `it` requires the descr... -
10:17 AM Feature #15897: `it` as a default block parameter
- Eregon (Benoit Daloze) wrote:
> What do you think about `_`?
> ...
I think Jon express my feelings with a clear example.
For `_` same thing. It is already use and it can lead to an issue: https://bugs.ruby-lang.org/issues/15897#note-3 -
- > I would appreciate feedback on whether this more detailed error message is an improvement.
I think this depends on what the ruby user at hand is doing; and how much expertise that
ruby user may have. Some behaviour in ruby can be c... -
- nobu (Nobuyoshi Nakada) wrote:
> Is “a Integer” OK? :)
"a(n) Integer" -
- Is “a Integer” OK? :)
-
01:15 AM Feature #11460: Unhelpful error message when naming a module with the same name as an existing class
- jeremyevans0 (Jeremy Evans) wrote:
> So I don't think there is a bug here. It is possible to change the format the error message, though. Attached is a patch that changes the error message to the include the current class of the objec... -
- Thanks to report. I'd like to know more about the context to fix the issue.
* Does the error happen at the same place when you retry running the tests?
* If so, could you share the output of the following command and all .c/.h files ... -
- I am trying to build the Ruby 2.7 snapshot for Fedora Rawhide [1], but I observe the following test failure on s390x and aarch64 platforms:
~~~
1) Failure:
TestJIT#test_block_handler_with_possible_frame_omitted_inlining [/builddir... -
-
- I would like to ask for clarification.
I understand that this feature removes the rule that complements argument-final brace-less key-value pairs with braces. That is, the rule that interprets:
```ruby
foo("bar", a: 1, b:2)
```
... -
-
-
-
-
- Applied in changeset commit:git|ee861e43f70d827abd1f8d26b2e97920237348b4.
----------
Skip indented comment lines [Bug #15981] -
- I was asked (apparently in private mail) about `^D` and `^C`. `^D` produces the same Traceback. `^C` produces another prompt, still with the number 001.
-
- I attached my .inputrc, and my .irbrc also just in case you might need that. I can't remember ever modifying these files in any way. I didn't even know there was a .inputrc file.
-
-
-
- * [Feature #11460] Unhelpful error message when naming a module with the same name as an existing class
-
- Let's look at this purely from a syntax point of view first, so that we can avoid
other issues such as backwards incompatible changes (which may be a big reason
why this request will not be implemented; but you have to ask matz).
I ... -
- There are other languages that use $ in string interpolation. One of them is Perl. Perl is much more famous and widely used than V. Ruby was created as a better Perl. $variable_name may work (most of the time, but not always) in language...
-
05:43 AM Feature #15983 (Rejected): Can we have a similar syntax (string interpolation) the way V language has?
- Sorry, guys, This is the first feature that I am writing in this Ruby issue tracking system, and If I make any mistake, please understand :).
Today I was going through this language, i.e. V language (mainly their website) and found it... -
- Applied in changeset commit:git|f19e048d244c709e2990ddbb0f986e8b51357bd2.
----------
Do not dispatch a nil token in ripper
As a comment token includes the newline, so delayed newline token
just follows it should not be dispatched. [Bu... -
- > `[ruby-core:<unknown>]`
This seems not having sent to the ML, and it happens sometimes, but I'm not sure why. -
- Thank you for the patch, somehow I've missed this issue at all.
`dispatch_delayed_token` is an empty expression unless ripper, so it is useless inside `#ifndef RIPPER`.
And delayed tokens should not be `nil` generally. -
- As a comment token includes the newline, so delayed newline token
just follows it should not be dispatched. [Bug #11485]
Co-Authored-By: Jeremy Evans <code@jeremyevans.net>