Activity
From 06/10/2022 to 06/16/2022
06/16/2022
-
10:50 PM Misc #18834: Significant change in loop speeds (regressing using while loop on ARM chips)
- Interesting! Can you post the output of:
$ ruby -ve 'pp RbConfig::CONFIG, RubyVM::OPTS'
For your ARM build of Ruby? I suspect the performance difference
could be explained by compiler differences. -
10:21 PM Misc #18834 (Feedback): Significant change in loop speeds (regressing using while loop on ARM chips)
I was benchmarking some code and one of the benchmarks I came across was <a href="https://github.com/fastruby/fast-ruby/blob/master/code/enumerable/each_with_index-vs-while-loop.rb">fast-ruby's</a> while vs each_with_index. I ran these...-
10:30 PM Feature #18835 (Open): Add InstructionSequence#type method
- This method returns a symbol representing the type of the instruction
sequence object.
I'm trying to collect some statistics about instruction sequences for an entire system, but I mostly care about methods and blocks. This feature l... -
- Follow up for 278fefb96294adf9d27a78f919c714a31b65ef58
-
08:25 PM Bug #18806 (Closed): protected methods defined by refinements can't be called
- Applied in changeset commit:git|ae163cae6b3f01e0fb827e0a18d5889f9703617f.
----------
Allow calling protected methods from refinements
Previously protected methods on refinements could never be called
because they were seen as being "de... -
04:14 AM Bug #18806: protected methods defined by refinements can't be called
- The option 1 is accepted.
Matz.
-
- Previously protected methods on refinements could never be called
because they were seen as being "defined" on the hidden refinement
ICLASS.
This commit updates calling refined protected methods so that they are
considered to be defined... -
06:57 PM Bug #17130: Method#super_method is broken for aliased methods
- It looks to me like super_method is still broken for aliased methods.
```
class A
def foo; end
end
class B < A
alias foo2 foo
end
p B.instance_method(:foo2).super_method #=> #<UnboundMethod: A#foo>
```
I believe that he... -
05:38 PM Feature #18159: Integrate functionality of syntax_suggest gem into Ruby
- Thank you everyone for your help so far. This is very exciting!
> like renaming
I did some brainstorming. I think having the word "syntax" in the name will help people remember or find it. Originally I scoped this to keywords `do` ... -
- I accept merging the functionality of `dead_end` gem to the core like `did_you_mean`. We have a few remaining issues like renaming it or separating `dead_end` command from the gem, etc.
Matz.
-
07:19 AM Feature #18159: Integrate functionality of syntax_suggest gem into Ruby
- We had a discussion today at the monthly committers' meeting, and there was general agreement to move ahead.
One point that was discussed was the name. It's a funny name, but it may not be easy to understand for beginners (compare e.g... -
06:58 AM Feature #18159: Integrate functionality of syntax_suggest gem into Ruby
- How about to move `::DeadEnd` to `::SyntaxError::DeadEnd` if it is only used for SyntaxError message modification?
(I don't know details so if it is not only for SyntaxError, please ignore this comment) -
05:13 PM Feature #18832: Do not have class/module keywords consider ancestors of Object
- I agree we shouldn't look in modules prepended/included in Object, only look on the lexical parent itself (not its ancestors).
This is one of these inconsistent "deep constant lookup" exceptions (the other I remember is "deepMethodSearc... -
04:59 PM Misc #18691: An option to build Ruby with build only flags not propagated to `rbconfig.rb`.
- > So, I want to add the ARCH_FLAG to configure script environment variables for convenience.
Just note. I tried to implement build only flags to inject ARCH_FLAG in Makefile with the patch below (the last commit on <https://github.com/j... -
- matz (Yukihiro Matsumoto) wrote in #note-24:
> > One way to address that is https://bugs.ruby-lang.org/issues/18751#note-11 (no longer hide ZSUPER method entry from users).
> ...
Could you point the incompatibility(ies)?
I think we ne... -
- > One way to address that is https://bugs.ruby-lang.org/issues/18751#note-11 (no longer hide ZSUPER method entry from users).
It is. And I once thought it was a good idea, but the change caused some incompatibility we don't want to se... -
- > On current TruffleRuby it's "B:hello" (same as current CRuby), due to that.
That's nice. It is an illusion we want to present.
Matz.
-
- matz (Yukihiro Matsumoto) wrote in #note-20:
> And if I understand correctly, copying could cause the following code to print "B:B:hello", which is confusing.
That depends on the details of super lookup, which can notice it should go... -
- @matz Right, this is the something you intended initially for public/protected/private.
I think most Rubyists do not understand this detail and the real practical issue is the inconsistencies shown by Method/UnboundMethod objects (e.g.,... -
- And if I understand correctly, copying could cause the following code to print "B:B:hello", which is confusing.
```ruby
class A
private def foo; puts "hello"; end
end
class B<A
private def foo; print "B:"; super; end
end
cl... -
- The current method searching is symbolic (not copying at the time) except for aliases intentionally. For example, if you redefine a method in a module after a class included the module, the redefined method is called. Aliasing is an exce...
-
04:49 PM Bug #18827 (Closed): `__ENCODING__` is not set to the source encoding when saving script lines
- Applied in changeset commit:git|cd5cafa4a380e2459862b6e99ff0c381362ef1be.
----------
Respect the encoding of the source [Bug #18827]
Do not override the input string encoding at the time of preparation,
the source encoding is not deter... -
- Do not override the input string encoding at the time of preparation,
the source encoding is not determined from the input yet. -
- Applied in changeset commit:git|278fefb96294adf9d27a78f919c714a31b65ef58.
----------
ENV.merge! support multile arguments [Feature #18279] -
- Accepted.
Matz.
-
-
03:48 PM Revision 51835135 (git): Added tests for setting ivars on frozen objs
-
- 03:47 PM Revision cfe9c24d (git): * 2022-06-17 [ci skip]
-
-
02:56 PM Revision 0ab2bca1 (git): [ruby/fileutils] [DOC] Small tweaks (https://github.com/ruby/fileutils/pull/89)
- https://github.com/ruby/fileutils/commit/13ab96439b
- 02:35 PM Revision c310691d (git): [ruby/net-http] Make `Net::HTTPHeader#content_range` return nil on non-byte units
- * Returning nil from the `content_range` method instead of raising an
error when the unit in the content-range header is not "bytes".
Fix https://bugs.ruby-lang.org/issues/11450
https://github.com/ruby/net-http/commit/0b5030dd86
Co-... -
02:19 PM Bug #18829 (Closed): GC_COMPACTION_SUPPORTED macro should be set and detected automatically.
- Applied in changeset commit:git|52d42e702375446746164a0251e1a10bce813b78.
----------
Rename GC_COMPACTION_SUPPORTED
Naming this macro GC_COMPACTION_SUPPORTED is misleading because it
only checks whether compaction is supported at compi... -
- Commit 0c36ba53192c5a0d245c9b626e4346a32d7d144e changed GC compaction
methods to not be implemented when not supported. However, that commit
only does compile time checks (which currently only checks for WASM),
but there are additional c... -
- Naming this macro GC_COMPACTION_SUPPORTED is misleading because it
only checks whether compaction is supported at compile time.
[Bug #18829] -
- This reverts commit 63546bfc1581d4abec2a0d846106a1c0afc0efa9.
-
- Probably intended to pass encoding "none".
https://github.com/ruby/racc/commit/65cd26efd8 -
- This function was added to a public header in [1] probably
unintentionally since it's not used anywhere, exposes implementation
details, and isn't related to the goals of that pull request.
[1]: 56cc3e99b6b9ec004255280337f6b8353f5e5b06 -
11:17 AM Bug #11450 (Closed): HTTPHeader.content_range throws error on non-byte units - Applied in changeset commit:git|63546bfc1581d4abec2a0d846106a1c0afc0efa9.
----------
HTTPHeader.content_range throws error on non-byte units
* Added a nil check in Net::HTTPHeader#initialize_http_header for keys in the header that do n... - 11:17 AM Bug #12055 (Closed): `NET::HTTPResponse` is not deflating responses with custom `Content-Range` header
- Applied in changeset commit:git|63546bfc1581d4abec2a0d846106a1c0afc0efa9.
----------
HTTPHeader.content_range throws error on non-byte units
* Added a nil check in Net::HTTPHeader#initialize_http_header for keys in the header that do n... - 11:16 AM Revision 63546bfc (git): HTTPHeader.content_range throws error on non-byte units
- * Added a nil check in Net::HTTPHeader#initialize_http_header for keys in the header that do not have any value
* Returning nil from the content_range method instead of raising an error when the unit in the content-range header is not by... -
-
- I prefer `Random::Formatter#alphanumeric(n = 16, chars: …)` to others. But `alphabet:` or `set:` are acceptable too.
Matz.
-
07:47 AM Revision 8ef312fc (git): MJIT: Consider compaction on CC failure
-
- In general, `a.b(&:c)` should behave exactly the same as `a.b{_1.c}`. But visibility check for `protected` methods may be too difficult for `to_proc`. So rejecting `protected` methods altogether like `private` methods is acceptable.
... -
- Rejected. Ruby and JavaScript are different languages.
Upon existence of `eval`, the impact of removing unused variables from closures are far bigger in Ruby. The optimization should not be mandatory.
If there's no side effect (e.g. `e... -
- Accepted. Unknown flags should raise errors.
Matz.
-
-
-
-
04:54 AM Bug #18833: Documentation for IO#gets is inaccurate (bytes versus characters)
- Correction - the `IO#gets` data for a UTF-8 input stream including BOM *does* include the BOM as an invisible first character. I didn't notice at first because it's, well, invisible!
Doesn't change the documentation issue at hand, but... -
- For avoidance of doubt, the behaviour of Ruby itself is (IMHO) sensible and working well. The only change needed is to alter the word "bytes" to "characters" for the `IO#gets` description of the `limit` parameter.
-
- Please see https://ruby-doc.org/core-3.1.2/IO.html#method-i-gets:
> With integer argument `limit` given, returns up to `limit+1` bytes:
In relation to https://github.com/janko/down/pull/74, I discovered that while `IO#read` ignores... -
- I am against the behavior change, because of the compatibility concern. It's OK for me to give warning instead of raising exceptions.
Matz.
-
-
06/15/2022
-
-
- This was a public method, so we should probably keep it.
-
-
09:49 PM Feature #18832: Do not have class/module keywords consider ancestors of Object
- You're right, it happens too if the first element of the nesting is `Object`.
For context, this happened in a Rails application that had `app/models/comment.rb`, which worked regularly fine. However, in a `.rake` file the project had ... -
09:08 PM Feature #18832: Do not have class/module keywords consider ancestors of Object
- fxn (Xavier Noria) wrote in #note-3:
> Even more, if you set an autoload for `C` in `Object`, the autoload is triggered. Which is also consistent with "I have not found the constant in my lookup, but let's trigger the autoload to get it... -
- Even more, if you set an autoload for `C` in `Object`, the autoload is triggered. Which is also consistent with "I have not found the constant in my lookup, but let's trigger the autoload to get it defined hopefully". This is also consis...
-
- There is something weird here somewhere.
In general, Ruby does not check the ancestors as far as I can tell. Take the same situation with non-empty nesting:
```ruby
module M
class C
end
end
module N
include M
cla... -
- I don't think this is a bug. `p Object.const_defined?(:C, false)` explicitly says you don't want to look into ancestors. However `class C` at top level will look into ancestors of Object (even `class Object::C` will). I don't believe R...
-
- The following code:
```ruby
module M
class C
end
end
include M
p Object.const_defined?(:C, false)
class C < String # (1)
end
```
prints `false`, as expected, but then raises `superclass mismatch for class C (Type... -
- https://github.com/ruby/fileutils/commit/ba3ae2430d
-
08:46 PM Revision 9eabc575 (git): [ci skip] [lldb] Ensure rbbt has loaded the globals
- rb_backtrace relies on the existend of RUBY_T_MASK. This is set up by
the global loading code in lldb_init()
rb_backtrace does not call lldb_init previously, and therefore would
only work if called after another lldb function that _did_... -
- Now that classes are using VWA, the RCLASS_PTR uses an offset to get the
rb_classext_t object. Doing this all the time in lldb is boring. So
script lldb to do it for us -
- follow up https://github.com/ruby/ruby/pull/6006
-
- just less C code to maintain
-
- Applied in changeset commit:git|1162523bae926cfa6128043b635e28c14b732754.
----------
Remove MJIT worker thread (#6006)
[Misc #18830] -
- Thank you for sharing your past usage of Ruby on Windows. I'll keep the MSWIN support during the changes of this ticket anyway, but note that you might not have been using MSWIN. If you installed Ruby with RubyInstaller2, it's MinGW. In ...
-
11:33 AM Misc #18830: Remove MJIT worker thread
- I am currently using Ruby with FreeBSD, macOS and GNU/Linux.
In the past I had to run Ruby with https://github.com/rails-sqlserver/tiny_tds in a Windows Server. About 4 years ago. -
- ## Proposal
* Remove MJIT worker thread
* Compiling ISeq to C should synchronously happen in Ruby threads
* Unix platforms asynchronously wait for a C compiler process to finish using SIGCHLD, and MSWIN synchronously waits for a... -
- [Misc #18830]
-
04:21 PM Feature #16495: Inconsistent quotes in error messages
- > the weird practice of putting three periods before and after a code block cited in a text
It is a cultural difference. In many languages/writing conventions, three dots is a sign of "phrase broken in the middle". Can be used when le... -
03:43 PM Feature #16495: Inconsistent quotes in error messages
- zverok (Victor Shepelev) wrote in #note-21:
> I wonder what is the **necessity** to preserve this legacy convention of ``assimetric `quotes'``?.. Just because it is already this way?.. (If you ask me, it irked me always as also looking ... -
02:20 PM Feature #16495: Inconsistent quotes in error messages
- zverok (Victor Shepelev) wrote in #note-21:
> (If you ask me, it irked me always as also looking weird in the terminal, but maybe it is something personal)(
Speaking of irking, the weird practice of putting three periods before and ... -
- @nobu Even where it works, it is not common knowledge of the way to hack around the **necessity** to post a singular backtick. Note that it was discovered in the current issue after **2 years of a discussion**. (I use markdown almost eve...
-
- As it seems working in other than titles, it would be an issue of GitHub.
You should report it to GitHub, not here. -
12:09 PM Feature #16495: Inconsistent quotes in error messages
- Not sure if it's well supported, it doesn't work in GitHub issue title which is one place where I have this problem.
https://github.com/socketry/async/issues/50 -
- https://daringfireball.net/projects/markdown/syntax#code
> To include a literal backtick character within a code span, you can use multiple backticks as the opening and closing delimiters:
> ...
> -
- > Why don't you use double- or triple-backticks?
Because that doesn't work for inline Markdown. -
- zverok (Victor Shepelev) wrote in #note-12:
> Because error messages are by their nature something you frequently want to communicate quickly and inline?
> ...
Why don't you use double- or triple-backticks?
> Ugh, do you know why a... - 04:04 PM Revision 64fb3279 (git): * 2022-06-16 [ci skip]
-
-
- `no_blockarg` is called for non-null `node` only.
-
- Block argument to `yield` is a syntax error.
This is because there was previously no way to receive a given block in the yielded block.
However `do |&block|` has been introduced since 1.8.7.
Why is it prohibited still now?
https:/... -
12:10 PM Revision d417c1dd (git): [rubygems/rubygems] Revert "Support running specs with asdf version manager"
- This reverts commit https://github.com/rubygems/rubygems/commit/4b2d09af5bc7.
https://github.com/rubygems/rubygems/commit/90ca7a7163 -
- The `asdf-ruby` plugin sets `RUBYLIB` to require some code to reshim
after installing gems. This interferes with our specs.
Reset that, but leave any "internal" entries in places, because the
ruby-core test setup also uses RUBYLIB.
htt... - 07:01 AM Revision daf086c0 (git): Update bundled gems list at 2022-06-15
-
-
- @vo.x With your patch and `--with-multiarch --with-archlibdir='${libdir}'`, not only libruby.so but also all standard library extensions are placed under `${libdir}` without `${arch}`.
Is this intentional? -
- The issue with #18487 was that `Kernel#binding` used to find the
first Ruby frame on the stack and that this iterating behavior
is brittle as it basically acts as an assertion that the frames
that it skips over remain as non-Ruby frames ...
06/14/2022
-
10:52 PM Bug #18780: Incorrect binding receiver for C API rb_eval_string()
- alanwu (Alan Wu) wrote in #note-15:
> I spoke too soon! Flipping the `if` in `demo.rb`:
> ...
Doesn't the change in https://bugs.ruby-lang.org/issues/18487 (raising a kernel error) imply that this doesn't need to be fixed?
Also, tha... -
- > I wrote a reproducer and luckily, it's no
> ...
I spoke too soon! Flipping the `if` in `demo.rb`:
```text
ruby 3.2.0dev (2022-06-14T16:06:06Z master ab10f111c3) [x86_64-darwin21]
[:rbeval_string, :main, :mainl]
"p [:in_main, sel... -
- Thanks for the bug report. The "binding with mixed information from two
contexts" situation from <https://bugs.ruby-lang.org/issues/18780#note-4>
definitely looks wrong. I wrote a reproducer and luckily, it's no
longer an issue on the... -
- * More on cp_r
https://github.com/ruby/fileutils/commit/82a2b62578 -
- Thank you for the ticket. I have [a patch](https://github.com/ruby/ruby/pull/6019) that should fix this issue, please try it out and let me know if it works.
-
- Since this problem does not occur in the master branch (due to the increased page size), it seems like the bug has already been fixed/worked around. It seems unlikely we would backport the increased page size to older Ruby versions, and...
-
10:58 AM Bug #18829 (Closed): GC_COMPACTION_SUPPORTED macro should be set and detected automatically.
- After backporting the patch [0] for GC compaction support from https://github.com/ruby/ruby/pull/5934 (for bug https://bugs.ruby-lang.org/issues/18779), I found that there is no mechanism to automatically define the GC_COMPACTION_SUPPORT...
-
- I agree with the @Eregon 's analysis, and submitted a pull request that makes Symbol#to_proc return a proc that will only call public methods: https://github.com/ruby/ruby/pull/6018 . I'm not happy with the implementation as it copies a...
-
- Also worth noting that for performance purposes, `Symbol#to_proc` should be able to be cached globally, i.e., cache the Proc in the/per Symbol instance.
So then the `self` inside that Proc should be a sentinel value (`nil` or the Symbol... -
- I think Symbol#to_proc should behave like `public_send`, i.e., only allows calling public methods.
That makes sense given we don't really have a call-site where we can assess the caller self easily, especially if converted to something ... -
- This appears to be caused by the use of the `VM_FCALL` flag in `vm_call_symbol`. Since `:foo.to_proc` should be treated as `lambda{|t| t.foo}`, not `lambda{|t| t.send(:foo)}`, I agree that this is a bug.
Fixing this for private metho... -
- Thank you both. As long as we have rb_mjit_header.h, I think we can work on it. I'll work on what @michals provided to close this issue.
-
05:17 PM Bug #18808: Cannot compile ruby 3.1.2 on powerpc64le-linux without disabling the jit features
- Line 22951-22953 of `rb_mjit_header.h`:
```c
__attribute__ ((__visibility__("default"))) extern
_Bool
rb_iseq_only_optparam_p(const rb_iseq_t *iseq)
```
Note the newline immediately following `extern`, which is unexpected by th... -
05:11 PM Bug #18808: Cannot compile ruby 3.1.2 on powerpc64le-linux without disabling the jit features
- ```
--- rb_mjit_header.h 2022-06-14 18:58:52.514742594 +0200
+++ rb_mjit_min_header-3.2.0.h 2022-06-14 07:47:37.415389264 +0200
...
@@ -22947,7 +16629,7 @@
((iseq)->body)->param.flags.has_kwrest == 0 &&
... -
- Given that this is not reproduced on RubyCI, I think this report is not actionable until we see an entire rb_mjit_header.h (not rb_mjit_min_header-3.2.0.h) that reproduces this problem. I'll leave this issue until somebody uploads one.
... -
- You can, but then the recipient should attach the files here anyway for everybody to be able to debug the issue with them. Do you have a browser to upload them yourself?
-
02:52 PM Bug #18808: Cannot compile ruby 3.1.2 on powerpc64le-linux without disabling the jit features
- Can I email these files to someone directly rather than post them here?
-
08:46 AM Bug #18808 (Assigned): Cannot compile ruby 3.1.2 on powerpc64le-linux without disabling the jit features
-
-
- ```
/tmp/20220614-16633-i2edux.h:16633:1: error: multiple storage classes in declaration specifiers
__attribute__ ((__visibility__("default"))) extern
^
compilation terminated due to -Wfatal-errors.
```
```
_Bool
rb_simple_iseq... -
- If `__attribute__ ((__visibility__("default")))` did not go with `extern` on a specific platform, then the following C code failed to compile:
```c
__attribute__ ((__visibility__("default"))) extern
int foo(void);
```
FWIW, with... -
- mame (Yusuke Endoh) wrote in #note-1:
> Just an idea. Is it possible to introduce a general instruction like `opt_newarray_send` instead of individual `opt_newarray_*` instructions?
It should be possible (IMO). But I guess it means ... -
- Just an idea. Is it possible to introduce a general instruction like `opt_newarray_send` instead of individual `opt_newarray_*` instructions?
- 04:06 PM Revision ab10f111 (git): * 2022-06-15 [ci skip]
-
- I tried to build Ruby on a system without libyaml today and realized
that my attempt from <https://github.com/ruby/psych/pull/557> doesn't
fix the error in <https://github.com/ruby/psych/issues/552>. I still got
the same `LoadError` from... -
- This commit makes YJIT allocate memory for generated code gradually as
needed. Previously, YJIT allocates all the memory it needs on boot in
one go, leading to higher than necessary resident set size (RSS) and
time spent on boot initiali... -
- * More on paths and lists
https://github.com/ruby/fileutils/commit/c3d92d34f4 -
- Applied in changeset commit:git|1a70973f7557af33bfca6e2edc5cd302937425a4.
----------
ripper: Check if anonymous parameters defined [Bug #18828] -
- https://github.com/ruby/ruby/pull/6016
-
- #### Anonymous rest parameter
```shell-session
$ ruby -c -e 'def b; c(*); end'
-e:1: no anonymous rest parameter
$ ruby -rripper -e 'p Ripper.new("def b; c(*); end").tap(&:parse).error?'
false
```
#### Anonymous keyword rest p... -
-
- * [Bug #18729] Method#owner and UnboundMethod#owner are incorrect after using Module#public/protected/private (eregon)
* Please see https://bugs.ruby-lang.org/issues/18435#note-12
* Removing "ZSUPER methods" solves everything: simp... -
02:31 AM Misc #18803: DevMeeting-2022-06-16
- * [Feature #18159] Integrate functionality of dead_end gem into Ruby (@duerst)
* How about this?
* IMO: We try to add `dead_end` as the default gems before releasing 3.2.0-preview2
-
- @mame san, thanks for letting me know about the discussion.
It looks to me that the discussion you quoted was directed toward letting `1..` be an alias of `1...`, just like https://bugs.ruby-lang.org/issues/18749#note-1 suggests, all ... -
- We were aware of this issue, and we agreed with the current behavior. This thread in Twitter discusses the issue: https://twitter.com/mrkn/status/987509913365594112
Here is a simple English translation:
* ko1: Under `ary = [1, 2, 3]`, ... -
- Okay thanks for your quick answer. @nobu Could you review the patch?
-
07:12 AM Bug #8973: Allow to configure archlibdir for multiarch
- Although I have not checked what is the situation with the `--with-rubyarchprefix` for a long time.
-
- Yes please! We still carry around the patch in Fedora:
https://src.fedoraproject.org/rpms/ruby/blob/rawhide/f/ruby-2.1.0-Enable-configuration-of-archlibdir.patch -
- @vo.x Do you still want this? I'd like to know if the patch is still need to review
-
- It would be easier to discuss if you could write a spec of what pattern match will pass what range. I understand as follows by reading your implementation. Right?
* `ary in [1, 2, 3]` will call `ary.deconstruct(3..3)`, which means "th... -
-
- Now the matrix library is a bundled gem, so (if needed) let's continue to discuss it in their bug tracker https://github.com/ruby/matrix.
-
- https://github.com/ruby/ruby/pull/6015
-
- `__ENCODING__` should respect the encoding of the given source code.
```shell-session
$ ruby -Ke -e 'p __ENCODING__'
#<Encoding:EUC-JP>
```
```ruby
p eval("__ENCODING__".encode("euc-jp")) #=> #<Encoding:EUC-JP>
```
But it is ig... -
03:31 AM Feature #18183: make SecureRandom.choose public
- > - `Random::Formatter#from_set(set, n = 16)` (or `Random::Formatter#from_set(n = 16, set: …)`)
I like `Random::Formatter#from_set` or `Random::Formatter#from_alphabet` because `from` makes it clear what the purpose of the additional ... -
- mame (Yusuke Endoh) wrote in #note-13:
> austin (Austin Ziegler) wrote in #note-11:
> ...
I think that `#alphanumeric` might still be the better name as the alphabet could be `[*'ABCDFGHKMNPQRTUVWXYZ'.split(''), *'0'..'9']`. If that’s ... -
- austin (Austin Ziegler) wrote in #note-11:
> One option would be to extend `Random::Formatter#alphanumeric` to have an optional "alphabet":
This approach looks nice to me. If "numeric" sounds a bit weird here, how about introducing `... -
06/13/2022
-
08:43 PM Bug #18826 (Closed): Symbol#to_proc inconsistent, sometimes calls private methods
- The following usage calls a protected method and prints "hello":
``` ruby
class Test
protected
def referenced_columns
puts "hello"
end
end
Test.new.tap(&:referenced_columns)
```
However, the follow... -
- > AbstractSyntaxTree already has script_lines for the sake of AST.of method. I think it's reasonable to make these lines accessible from SyntaxError too.
That is perfect. Not having to read in a file to get contents makes this much ea... -
- @schneems If this proposal was accepted, can you transfer `dead_end` to under the ruby organization? The ruby committer needs to develop the upstream because the change of Ruby interpreter broke the default gems.
It's great to fix it ... -
- nobu (Nobuyoshi Nakada) wrote in #note-1:
> I think you can pass build-time-only flags to `make`:
> ...
I tested. And I see that the `make install` also needs the `ARCH_FLAG` to build some native extension gems.
```
$ make install ... -
- > > https://github.com/ruby/ruby/pull/5879
> ...
As you know, the PR to add `configure --enable-mkmf-verbose` option above was merged.
-
- I merged it.
-
- And re-embed any strings that can now fit inside the slot they've been
moved to -
- Feature #18611 is merged. That feature encourages people to write hash methods like this:
```
def hash
[@a, @b, @c].hash
end
```
I would like to add a specialized instruction for this case `opt_newarray_hash`. It's similar ... -
- Removed in commit:f8502a26990c652a2c3c1131614230fec446ab25
-
- ## Proposal
Stop supporting MJIT on MinGW from Ruby 3.2
## Motivation
Compilers on MinGW behave weirdly and MinGW-specific C code is sometimes required as a workaround. Despite the high maintenance cost, nobody seems to be using MJI... -
- [Feature #18824]
- 03:39 PM Revision c3ee80ff (git): * 2022-06-14 [ci skip]
-
- https://github.com/ruby/fileutils/commit/5f9ef9ddc8
-
- Thanks for the clarification.
I see that ruby core uses bool pretty consistently, and _Bool is used only in a few places.
Not sure where I copied it from. -
- michals (Michal Suchánek) wrote in #note-6:
> include/ruby/internal/stdbool.h defines _Bool, and in most cases just uses bool defined by the runtime.
No. C99 defines "_Bool" as an intrinsic type, and C's stdbool.h defines "bool" as a... -
- include/ruby/internal/stdbool.h defines _Bool, and in most cases just uses bool defined by the runtime.
I have no idea how there would even be _Bool if not defined there.
_Bools is used in bigdecimal and detected in extconf so it's... -
- michals (Michal Suchánek) wrote in #note-3:
> I added a _Bool argument as part of other development which prevents ruby from building on older compiler versions and VS - eg. https://github.com/ruby/ruby/commit/6c72653d98c36c2a816bfff4e4... -
- ```
generating cxxanyargs-x64-mswin64_140.def
compiling ../../../../src/ext/-test-/cxxanyargs/cxxanyargs.cpp
cxxanyargs.cpp
D:\a\ruby\ruby\src\include\ruby/internal/intern/select/win32.h(213): error C2061: syntax error: identifier '_... -
- I added a _Bool argument as part of other development which prevents ruby from building on older compiler versions and VS - eg. https://github.com/ruby/ruby/commit/6c72653d98c36c2a816bfff4e4e9b1c451154a9e
-
- > When a _Bool argument is added to rb_fd_select
I cannot understand what do you mean. Could you elaborate how to reproduce your issue and show the error log? -
01:46 PM Bug #18816: Ractor segfaulting MacOS 12.4 (aarch64 / M1 processor)
- I've tried to reproduce the problem in a container running from the M1 mac as host, but it seems the issue is mac-specific, as I couldn't make it SEGV.
```
Linux ac9a228ca7ac 5.15.40-0-virt #1-Alpine SMP Wed, 18 May 2022 08:12:19 +00... -
- Treats:
::chown_R
::touch
::commands
::options
::have_option?
::options_of
::collect_method
https://github.com/ruby/fileutils/commit/5df0324f52 -
10:33 AM Revision b1397e96 (git): [ruby/reline] Revert "Merge pull request #441 from nevans/workaround-linker-script-so"
- This reverts commit https://github.com/ruby/reline/commit/4ccf128ffa18, reversing
changes made to https://github.com/ruby/reline/commit/a2651419e9a0.
https://github.com/ruby/reline/commit/51053138a4 - 10:12 AM Revision a80f5c53 (git): Enable "make annocheck" on platforms other than Linux.
- The annocheck supports ELF format binaries compiled for any OS and for any
architecture. It can work in not only Linux but also FreeBSD and Solaris.
It is designed to be independent of the host OS and the architecture.
Even in Mac, as t... -
- ... because insns_info_index could not be zero here. Also it adds an
invariant check for that.
This change will prevent the following warning of GCC 12.1
http://rubyci.s3.amazonaws.com/arch/ruby-master/log/20220613T000004Z.log.html.gz
... -
- ... by assigning a dummy value to the allocated stack.
http://rubyci.s3.amazonaws.com/arch/ruby-master/log/20220613T000004Z.log.html.gz
```
cont.c: In function ‘cont_restore_0.constprop’:
cont.c:1489:28: warning: ‘*sp’ may be used unini... - 04:12 AM Revision 425a4613 (git): Handle case where write result is zero.
-
- It sent the char to check even to non-tty, e.g., pipe.
This causes `unknown command: "\xE2\x96\xBDstart ` warnings on
ruby's parallel test on Windows, where non-standard FDs cannot be
passed to child processes.
https://github.com/ruby/r... -
- 01:38 AM Revision 54be0e4f (git): * 2022-06-13 [ci skip]
-
- http://rubyci.s3.amazonaws.com/ubuntu1804/ruby-master/log/20220613T003003Z.log.html.gz
```
/home/chkbuild/chkbuild/tmp/build/20220613T003003Z/ruby/test/ruby/test_yjit_exit_locations.rb:96: warning: assigned but unused variable - out
/hom... -
- I cannot reproduce the issue with Ubuntu 20.04 on ppc64le. Could you provide config.log?
06/12/2022
-
- Apparently for MSVC to report the correct c++ version it needs the /Zc:__cplusplus flag.
I don't know where to inject this flag, though.
The other failure cases are probably really obsolete.
-
- When a _Bool argument is added to rb_fd_select ruby cannot be compiled on
VisualStudio 2022
VisualStudio 2019
gcc-5
gcc-4.8
clang-5
clang-4
clang-3.9
c++98 (llvm 14)
c++2a (llvm 14)
which suggests that `if defined(HAV... -
- ```
diff --git a/tool/transform_mjit_header.rb b/tool/transform_mjit_header.rb
index 8867c556f0..63a072573a 100644
--- a/tool/transform_mjit_header.rb
+++ b/tool/transform_mjit_header.rb
@@ -194,10 +194,10 @@ def self.conflicting_types?(... -
- Also a problem on SLE 12
Deleting the `extern` reports the same error on the next line with `__attribute__ ((__visibility__("default"))) extern` which suggests that `extern` does not go with `__attribute__ ((__visibility__("default")))`... -
- daveola (David Stellar) wrote in #note-11:
> I hear the suggestion and I will just have to switch to using a debugger for my code to work, it's not a conditional, I need the ability to write a different version of eval() for my code, and... -
- schneems (Richard Schneeman) wrote in #note-19:
> One idea: In addition to the `SyntaxError#path`, is it possible to also attach the source code the parser was just looking at maybe an API like `SyntaxError#source_contents`?
`Abstrac...
06/11/2022
-
- Eregon (Benoit Daloze) wrote in #note-10:
> I'm reluctant to reply since you seem to ignore my comments as a Ruby implementer.
I'm sorry you feel that way, and I regret posting to the truffleruby discussion by mistake, I lost track o... -
- I'm reluctant to reply since you seem to ignore my comments as a Ruby implementer.
Anyway, you are asking for something to get the caller's binding, that is very much on purpose not provided by Ruby.
Such a functionality breaks encapsul... - 05:02 PM Revision ee7aca31 (git): * 2022-06-12 [ci skip]
-
- These gemspecs already work most of the times. When they are installed
normally, the require_paths in the gemspec stub line becomes actually
correct, and the incorrect value in the real gemspec is ignored. It only
becomes an issue in sta... -
12:26 PM Revision 28e27ee7 (git): Fix typo in yjit.c comments [ci skip]
-
11:17 AM Bug #18767: IO.foreach hangs up when passes limit=0
- I agree that the current behaviour completely makes sense.
The point is that there are other IO methods (that read multiple lines) which don't accept 0 as a limit. So it's more a consistency issue.
For instance `IO.readlines` and `IO#e... -
- Previously we would instantiate two different packages and extract the
specification from the package twice for each gem installed. We can
reuse the installer for this so that we just need to do it once.
https://github.com/rubygems/ruby... -
- https://github.com/rubygems/rubygems/commit/ba975b3b7f
-
- https://github.com/rubygems/rubygems/commit/600a9ac658
-
- This is the explanation of why we do the swapping, not of why we
download the gem.
https://github.com/rubygems/rubygems/commit/1a25eb7e7b -
- https://github.com/rubygems/rubygems/commit/796eebfdbf
-
- https://github.com/rubygems/rubygems/commit/9bd389e1b6
-
- It's only related to the `bundle cache` command, so it should be checked
there.
https://github.com/rubygems/rubygems/commit/cf749f8ffa -
- https://github.com/rubygems/rubygems/commit/285ccbc07e
-
- https://github.com/rubygems/rubygems/commit/d86fb2c316
-
- https://github.com/rubygems/rubygems/commit/04e6a5ae31
-
- These days all these errors are raised as `Gem::Security::Exception` so
there's no need to do any matching on the exception message.
https://github.com/rubygems/rubygems/commit/bd3403da57 -
- The `security_policies` method already requires it.
https://github.com/rubygems/rubygems/commit/d19b088f2f -
- It's checked before calling the method already.
https://github.com/rubygems/rubygems/commit/4eb00e9586 -
- https://github.com/rubygems/rubygems/commit/a00c79a4da
- 05:22 AM Revision 7e1788e1 (git): fix typo in dir documentation (#6002)
-
- Applied in changeset commit:git|e75cb61d4645b9833b14a0cc4190cceffc9b6551.
----------
Fix nested bmethod TracePoint and memory leak
df317151a5b4e0c5a30fcc321a9dc6abad63f7ed removed the code to free
rb_hook_list_t, so repeated targeting ...
06/10/2022
-
- Previously, because opt_aref and opt_aset don't push a frame, when they
would call rb_hash to determine the hash value of the key, the initial
level of recursion would incorrectly use the method id at the top of the
stack instead of "has... -
-
- Treats ::chmod_R and ::chown.
https://github.com/ruby/fileutils/commit/df4ac84bef -
- I 100% agree. I think we should aim to get it into a preview and ideally get another preview release. If people have a strong reaction against it, then we don't need to invest more time. If people see it being helpful then we can work mo...
-
- schneems (Richard Schneeman) wrote in #note-19:
> It's maybe worth asking as well, how confident is Ruby core that this is a feature they want? Basically: I am worried that if I ask you for too many changes or new interfaces and then ... -
- 05:52 PM Revision 9ed9cc98 (git): Add tests for a variety of string-subclass operations (#5999)
- This way YJIT has to match CRuby for each of them.
Remove unused string_p() Rust function - 04:29 PM Revision 46333f59 (git): * 2022-06-11 [ci skip]
- 04:29 PM Revision e777ac91 (git): Don't return a value from jit_guard_known_klass. We never return anything but true at this point and we don't usually check the returned value. (#6000)
-
- mame (Yusuke Endoh) wrote in #note-8:
> @jeremyevans0 Thank you for your explanation, I understand. The keyword name "chomp" might be a bit confusing.
I agree, the behavior is not obvious from the name `chomp`. However, it is obviou... -
- @jeremyevans0 Thank you for your explanation, I understand. The keyword name "chomp" might be a bit confusing.
-
- * print `ruby_debug_log_mode` at first.
* show filters when `ruby_debug_log_mode` is not "disabled". - 02:12 PM Revision c54f4264 (git): Remove duplicated rb_yjit_get_stats (#5997)
- `rb_yjit_get_stats` is defined twice in yjit.c, it only needs to be
defined once. -
12:11 PM Feature #11164: Garbage collector in Ruby 2.2 provokes unexpected CoW
- That seems to be exactly what https://github.com/ko1/nakayoshi_fork solves anyway.
-
- This ticket raised GC's efficiency issue. As far as I read, it was not a regression. I consider that this is not a bug, but a suggestion for improvement. I'd like to move this to the Feature tracker, and close it for now because I don't ...
-
10:58 AM Bug #18771 (Closed): IO.foreach/.readlines ignores the 4th positional argument
- Applied in changeset commit:git|27eb36596a65d6bca44b4420ca6526175bf1b431.
----------
Stop ignoring 4th positional argument to IO.#{foreach,readlines}
Fixes [Bug #18771] -
- Maybe because of time, I cannot understand what is a problem. What do you mean "ignored"?
A bundled gem has been used for many years as a bare gem that is automatically installed during "make install" (i.e., it can be uninstalled), an... -
- I believe this is not a bug. The current YARV compiler is a product of trial and error, and we know that sometimes it emits dead code (mainly due to peephole optimization). It may be room for improvement, but not a bug.
-
- According to the OP, there is the same issue in Ruby 3.0 and the same fix works for Ruby 3.0. Continue to discuss it in #18049. Closing this.
-
- I found two bug reports in other projects that have a similar stack trace:
https://github.com/lastpass/lastpass-cli/issues/170
https://www.mail-archive.com/macports-users@lists.macports.org/msg07932.html
Both are on El Capitan. I ... -
- I tried the script on Windows 11 / WSL2 Ubuntu 22.04, but couldn't repro the issue. I guess WSL2 solved the issue. Please ping me if it still occurs.
-
- For the third and forth examples, you can use `BOM|UTF-8` encoding.
```
$ ruby -e 'p File.read("utf-8-with-bom-file", encoding: "BOM|UTF-8").ascii_only?'
true
$ ruby -e 'p File.read("utf-8-with-bom-file", encoding: "BOM|UTF-8")[0]'... -
- Does this still reproduce?
-
- I believe this is a spec of Windows. Ruby's IO interface is based on C's stdio, and I confirmed that `fwrite("Hello\n", 1, 6, fp)` returns 6 and actually outputs 7 bytes on Windows with cl.exe.
-
- The more pervasive Markdown becomes, the more annoying this quoting style becomes.
-
- df317151a5b4e0c5a30fcc321a9dc6abad63f7ed removed the code to free
rb_hook_list_t, so repeated targeting of the same bmethod started
to leak the hook list. You can observe how the maximum memory use
scales with input size in the following...