Activity
From 10/28/2020 to 11/03/2020
11/03/2020
-
10:09 PM Revision bf1047c7 (git): Update NEWS for Array methods change
-
- Applied in changeset commit:git|2a294d499bf03211d02695f613f784a05943ea35.
----------
Make Array methods return Array instances instead of subclass instances
This changes the following methods to return Array instances instead
of subcla... -
- This changes the following methods to return Array instances instead
of subclass instances:
* Array#drop
* Array#drop_while
* Array#flatten
* Array#slice!
* Array#slice/#[]
* Array#take
* Array#take_while
* Array#uniq
* Array#*
Fixes [... -
09:14 PM Feature #17298: Ractor's basket communication APIs
- Eregon (Benoit Daloze) wrote in #note-15:
> `Ractor#receive_and_sender` (aka `recvfrom` but with a proper name) and `Ractor.yield_and_sender` would be enough for that, right?
Yes, it is enough. However, the name is too long and ambiguou... -
08:20 PM Feature #17298: Ractor's basket communication APIs
- ko1 (Koichi Sasada) wrote in #note-14:
> Beside the performance, I want to use it for the features:
> ...
`Ractor#receive_and_sender` (aka `recvfrom` but with a proper name) and `Ractor.yield_and_sender` would be enough for that, right... -
- Beside the performance, I want to use it for the features:
> Ractor::Basket#sender returns the sending ractor.
> ...
-
08:25 PM Misc #17299: DevelopersMeeting20201120Japan
- * [Bug #17197] Yielding arity for `Hash` methods (marcandre)
* `Hash#each` with arity 1: confirmed?
* `#select`, `#keep_if`, `#delete_if`, `#reject` and `to_h` should also be changed, right?
* `#map`: should only accept arity 1,... -
10:13 AM Misc #17299: DevelopersMeeting20201120Japan
- * [Feature #13381] Expose rb_fstring and its family to C extensions (byroot)
* The feature itself was approved, however we're still waiting on an agreement on the naming of one function (https://github.com/ruby/ruby/pull/3586)
* Bo... - 03:55 PM Revision 7d6c72dc (git): * 2020-11-04 [ci skip]
-
03:51 PM Revision 70063757 (git): Rightward assignment is replaced by one-line pattern matching
-
- Specifically,
```ruby
it "raises TypeError if one of the passed exceptions is not a Module" do
-> {
@s.rb_rescue2(-> *_ { raise RuntimeError, "foo" }, :no_exc, -> x { x }, :exc, Object.new, 42)
}.shou... -
02:32 PM Revision c3e2dd07 (git): test/ruby/test_gc_compact.rb: suppress "assigned but unused variable"
-
01:25 AM Revision fa748401 (git): Add links to the tickets [ci skip]
-
12:48 AM Revision 4f7d27a2 (git): Fix typo in the auto compact announcement [ci-skip]
- I'm sorry, but I think there is a typo here.
This fix will help folks who are trying to translate this announcement to other languages. I hope this is not a joke and I didn't get it 🙏
11/02/2020
-
11:57 PM Bug #17304 (Feedback): Ruby stuck calling sched_yield on fork
- Can you reproduce this issue with the master branch, or at least Ruby 2.6 or 2.7? The code you posted from Ruby 2.5 is no longer present in Ruby 2.6 or later versions. Ruby 2.5 is in security maintenance mode, and this doesn't appear t...
-
12:51 PM Bug #17304 (Closed): Ruby stuck calling sched_yield on fork
- We have been encountering intermittent bug when using fork - the interpreter process gets stuck in a loop that keeps calling sched_yield. This keeps happening seemingly randomly every few days, while working correctly most of the time. (...
-
10:43 PM Feature #17176 (Closed): GC.auto_compact / GC.auto_compact=(flag)
- Applied in changeset commit:git|67b2c21c327c96d80b8a0fe02a96d417e85293e8.
----------
Add `GC.auto_compact= true/false` and `GC.auto_compact`
* `GC.auto_compact=`, `GC.auto_compact` can be used to control when
compaction runs. Settin... - 10:43 PM Revision 46f3b68f (git): * 2020-11-03 [ci skip]
-
- * `GC.auto_compact=`, `GC.auto_compact` can be used to control when
compaction runs. Setting `auto_compact=` to true will cause
compaction to occurr duing major collections. At the moment,
compaction adds significant overhead to ... -
- * [Feature #17143] Improve support for warning categories (jeremyevans0)
* I researched the Python warning categories, and provided some analysis.
* Can we decide on warning categories so they can be implemented in time for Ruby 3?... -
11:15 AM Misc #17299: DevelopersMeeting20201120Japan
- * [Feature #17303] Make webrick to bundled gems or remove from stdlib
* Any objection?
-
- It seems like the more fundamental thing we need is more maintainers for WEBrick.
Even if it's removed from stdlib, people will still install it for some existing use cases. -
- Doesn't RubyGems depend on WEBrick (notably for `gem server`)?
It seems also RDoc depends on it.
And I know `ruby -run -e httpd . -p8080` depends on it as well.
I think having a basic HTTP server in stdlib is important (bundled gem ... -
- I am in favor of this change. I prefer removing webrick from stdlib, as otherwise we are still likely to be shipping vulnerable code if there is a security issue in webrick. Moving webrick from default gems to bundled gems doesn't chan...
-
- I propose to move webrick to bundled gems or remove it from stdlib of ruby.
We have several vulnerability issues in webrick gem.
https://www.ruby-lang.org/en/news/2020/09/29/http-request-smuggling-cve-2020-25613/
The ruby core t... -
- ko1 (Koichi Sasada) wrote in #note-10:
> I rewrote copying logic without marshal protocol (https://github.com/ruby/ruby/pull/3728).
That is great!
I remember doing something quite similar in https://eregon.me/thesis/mozart2slides.... -
- marcandre (Marc-Andre Lafortune) wrote in #note-11:
> The use-case seems unusual:
> ...
That sounds like the perfect anti-pattern to me, so agreed this new APIs seem overkill for now and not worth it.
If it's a big object:
* If it ... -
- The use-case seems unusual:
- Need to send very big object to a Ractor
- That object can not be deep-frozen for some reason, or moved so it deep-copied
- The receiving Ractor needs to send it to another Ractor
Even given this "extr... -
- I rewrote copying logic without marshal protocol (https://github.com/ruby/ruby/pull/3728).
Additional benchmark:
```ruby
Warning[:experimental] = false
if ENV['MODE'] == 'share'
MODE = :copy
SHAREABLE = true
else
MODE... -
02:31 PM Feature #16604: Set default for Encoding.default_external to UTF-8 on Windows
- @usa @nobu @naruse Could you please take a look at this request? I pushed an updated patch here: https://github.com/ruby/ruby/pull/2877
-
01:49 PM Revision 79b24226 (git): ripper: Invalid pragma value warning
-
-
-
07:58 AM Bug #17302: The TracePoint API does not allow setting multiple line traces within the same method (ISEQ)
- liran.last@gmail.com (Liran Haimovitch) wrote in #note-1:
> liran.last@gmail.com (Liran Haimovitch) wrote:
> ...
After some additional investigation, it seems that when adding multiple breakpoints to the same method (ISEQ) only the las...
11/01/2020
-
- Now copying objects do not need marshal protocol.
-
- This bug occurs inside a 3rd party C extension. From the backtrace:
```
/lib64/libc.so.6(0x7fde5f1185a0) [0x7fde5f1185a0]
/usr/lib64/liby2.so.4(_ZN17Y2PluginComponent10loadPluginEPKc+0x688) [0x7fde5d8ea208]
/usr/lib64/liby2.so.4(_... -
08:37 AM Bug #17301 (Third Party's Issue): /sbin/yast2: line 468: 3147 Aborted
- Starting the software administration fails with a core dump.
Ruby version
ruby 2.5.8p224 (2020-03-31 revision 67882) [x86_64-linux-gnu]
Kernel version
OpenSUSE
Linux 5.3.18-lp152.47-default #1 SMP Thu Oct 15 16:05:25 UTC 2020 (4... - 04:37 PM Revision 1581da99 (git): * 2020-11-02 [ci skip]
-
- This patch allows to move more data types.
-
- liran.last@gmail.com (Liran Haimovitch) wrote:
> When setting a second line tracepoint within a method the first one will be turned off.
> ...
Attaching a short file to reproduce the bug, based on the existing `enable_spec.rb` in the R... -
- While setting a tracepoint for a line for the second time within a method, the first one turns off.
I believe this is because the `encoded_iseq_trace_instrument` function resets the trace value of an instruction rather than just turni... -
-
-
- https://github.com/ruby/ruby/runs/1337845174
-
- I prefer pconst to be the first element of NODE.
Before:
| ARYPTN | FNDPTN | HSHPTN
---+--------+--------+-----------
u1 | imemo | imemo | pkwargs
u2 | pconst | pconst | pconst
u3 | apinfo | fpinfo | pkwresta... - 05:12 AM Revision 305c79af (git): ext/socket/rubysocket.h: avoid the conflict of T_DATA definition in AIX
-
- 04:36 AM Revision b1e7c3a3 (git): * 2020-11-01 [ci skip]
-
10/31/2020
-
- BTW, for `recvfrom` feature, we need more 2 APIs.
This API can cover this feature (and it is more extendable), so I don't think "4" APIs are heavy. -
- Eregon (Benoit Daloze) wrote in #note-4:
> For the first example, isn't `move: true` much simpler?
There are two problems:
* Now, many types are not support on `move: true`. I'll investigate more, but not sure we can support for all da... -
- In the example above, using `, move: true` for Ractor.yield and Ractor#send, instead of the `_basket` calls seems to give the same or better performance.
(code at https://gist.github.com/eregon/092ea76534b46e227d9cbf5fd107de66)
It runs... -
- From the benchmark above, USE_BASKET=false takes for me `5.636s`.
Adding `Ractor.make_shareable(ary)`, it takes `0.192s`.
So that's ~10x faster than with `w/ basket API` on this benchmark, and does not require new APIs and concepts.
... -
- For the first example, isn't `move: true` much simpler?
```ruby
bridge = Ractor.new do
Ractor.yield Ractor.receive, move: true
end
consumer = Ractor.new bridge do |from|
obj = from.take
do_task(obj)
end
msg = [1, 2, 3]
bridge.sen... -
- When looking at replacing `kernel_sleep` by `blocking`, I found an independent bug.
ConditionVariable does not seem to work with the Fiber scheduler currently.
There is an existing test in https://github.com/ruby/ruby/blob/4f8d9b0db84c... -
02:56 AM Revision 4f8d9b0d (git): Revert "Use adjusted sp on `iseq_set_sequence()`" and "Delay `remove_unreachable_chunk()` after `iseq_set_sequence()`"
- This reverts commit 3685ed7303fc08bf68cd3cc8d11e22a8ce63a067 and 5dc107b03f5cf32656a5308574b90458486c633c.
Because of some CI failures https://github.com/ruby/ruby/pull/3404#issuecomment-719868313. -
- [ci skip]
-
-
12:56 AM Feature #17294: Feature: Allow method chaining with Pathname#mkpath Pathname#rmtree
- I would like this too. I've been using [Refinements](https://www.alchemists.io/projects/refinements/#_pathname) to improve Pathname behavior but this would be better.
-
- # The next dev meeting
**Date: 2020/11/20 13:00-17:00**
Place/Sign-up/Agenda/Log: https://github.com/ruby/dev-meeting-log/blob/master/DevelopersMeeting20201120Japan.md
- Dev meeting *IS NOT* a decision-making place. All decisions ... -
-
-
10/30/2020
-
11:47 PM Revision 670e288d (git): Add warning for str_new_static functions
- Many functions in string.c assume that capa + termlen to be readable
memory. Add comment in header to communicate this to extension authors.
See also: comment in str_fill_term() -
-
- I tried pull request #3624 on OpenBSD/sparc64 and it still crashed.
I was able to come up with a fix that works on OpenBSD/sparc64, as long as a couple files are compiled without optimization: https://github.com/ruby/ruby/pull/3726 - 07:22 PM Revision bd6cd851 (git): Tweak return of `Ractor#close`, add doc
-
- This ticket proposes `send_basket`/`receive_basket`, `yield_basket`/`take_basket` APIs to make effective and flexible bridge ractors.
## Background
When we want to send an object as a message, we usually need to copy it. Copying is... - 04:48 PM Revision 7c548278 (git): * 2020-10-31 [ci skip]
-
- `r = Ractor.new{ expr }` generates the block return value from `expr`
and we can get this value by `r.take`. Ractor.yield and Ractor#take
passing values by copying on default. However, the block return value
(we named it "will" in the co... -
- greg.howdeshell (Greg Howdeshell) wrote:
> URI.parse looks to fail parsing endpoints that have special characters. For example:
> ...
This is expected. The `#/applications/` is an anchor/fragment, not part of the path (path is `/`). ... -
02:58 PM Bug #17293 (Rejected): URI.parse fails to parse correctly URN or other special characters in path/url
- URI.parse looks to fail parsing endpoints that have special characters. For example:
``` ruby
url = 'http://foobar.com/#/applications/'
path = 'my_application'
URI.join(url, path).to_s
```
The result renders `http://foobar.com/my... -
03:09 PM Feature #17297 (Closed): Feature: Introduce Pathname.mktmpdir
When I want to create a tmpdir I often want to manipulate it as a pathname. By introducing Pathname.mktmpdir I can get this behavior.
Currently I must:
```ruby
Dir.mktmpdir do |dir|
dir = Pathname(dir)
# ... code
end
``...-
The `FileUtils.chmod` provides the same numerical interface as `File.chmod` and it also includes a "symbolic mode" interface. With this patch you'll be able to run this code:
```ruby
Pathname.new("bin/compile").chmod("+x")
```
...-
Right now if a developer wants to create a file and is not sure if the path exists yet or not they must:
```ruby
Pathname.new("/a/b/c/d.txt").tap {|p| p.dirname.mkpath; FileUtils.touch(p)}
```
After this patch a developer can...-
Currently in my code when I want to create a pathname object and create a path at the same time I must use tap
```
path = Pathname.new("/tmp/new").tap(&:mkpath)
```
I think it would be cleaner to be able to chain on the results...-
- It have no upstream repo yet. This change is experimental for 3.0.0-preview2.
-
10:07 AM Feature #17277: Make Enumerator#with_index yield row and col indices for Matrix
- sawa (Tsuyoshi Sawada) wrote in #note-7:
> I think the current behaviour is natural. You cannot play around with `with_index` since its receiver is `Enumerator`, not `Matrix`, and the information as a matrix is already gone.
> ...
I ge... -
-
- sorry to be late, but I can't reproduce this issue.
`while PUTS_RACTORS=1 WORK=shell make run; do date; done` doesn't show any errors on my environment (ruby 3.0.0dev (2020-10-29T15:09:12Z master 502d6d8459) [x86_64-linux]).
recent... -
- a method defined by define_method with normal Proc can not cross
ractors because the normal Proc is not shareable. However,
shareable Proc can be crossed between ractors, so the method with
shareable Proc should be called correctly. -
- vm->waiting_fds is global resource so we need to lock it correctly.
(forgot to sync one place) -
- But win32ole gem is still experimental for 3.0.0-preview2.
I'm working to extract this library on https://github.com/ruby/win32ole. -
-
-
12:21 AM Feature #17291: Optimize __send__ call
- I'm neutral (at least no against it). `__send__` in general has other usages than to reroute method visibilities. Optimising it could benefit good wills.
-
- JFYI I learned the use of "immediate" refinement from rails.
https://github.com/rails/rails/pull/27363 -
- chrisseaton (Chris Seaton) wrote in #note-14:
> I think there's benefits to building STM into the language (if we decided we want STM at all) rather than it being a library.
I think so, especially with Ractors, but now we (*I*) don't...
10/29/2020
-
08:54 PM Feature #17261: Software transactional memory (STM) for Threads and Ractors
- I think there's benefits to building STM into the language (if we decided we want STM at all) rather than it being a library.
When you look at more advanced features like conflict resolution and conflict mitigation you may want to do ... -
- Eregon (Benoit Daloze) wrote in #note-12:
> I was talking about the namespace
Ah, I see.
-
- ko1 (Koichi Sasada) wrote in #note-11:
> You wrote "under Thread and not under Ractor". What does it mean?
I was talking about the namespace, the proposal is Thread::TVar (and not Ractor::TVar), which I agree is a good namespace for ... -
- Eregon (Benoit Daloze) wrote in #note-10:
> That does not work with Ractor though (at least currently).
You wrote "under Thread and not under Ractor". What does it mean?
-
- ko1 (Koichi Sasada) wrote in #note-8:
> For this purpose, concurrent-ruby provides TVar for threads.
That does not work with Ractor though (at least currently). -
-
- > I think it would be nice to make it its own gem (tvar maybe?) given it's under Thread and not under Ractor, and it could most likely work on other Ruby implementations (e.g., TruffleRuby).
For this purpose, concurrent-ruby provides ... -
- How about a private module instead?
```ruby
class Foo
module Helpers
def self.special # General users should not call or rely on `special`
:special
end
end
private_constant :Helpers
def foo
Helpers.special
en... -
- shyouhei (Shyouhei Urabe) wrote in #note-9:
> @marcandre Here you are:
> ...
0) I was wrong, I retract what I said.
1) My mind is blown. I have always thought of refinements as a way to safely monkey-patch other people's classes, in... -
- @marcandre Here you are:
```ruby
class Foo
using Module.new {
refine Foo.singleton_class do
def special
end
end
}
def foo
self.class.special
end
class Bar
def foo
Foo.specia... -
- Eregon (Benoit Daloze) wrote in #note-16:
> Eregon (Benoit Daloze) wrote in #note-14:
> ...
I agree that it's relatively rare and not a good idea. However, Sequel does this (Sequel::DATABASES). It's been around since 2008 and many ex... -
- Eregon (Benoit Daloze) wrote in #note-16:
> I guess it's relatively rare that a gem would (intentionally) expose a non-frozen constant as part of its API, and that the gem relies on being able to mutate it.
To confirm it, we will int... -
- Eregon (Benoit Daloze) wrote in #note-14:
> Of course, no gems should directly mutate constants of another gem.
I missed that the gem doesn't need to mutate `A` to break `OtherLib`.
I guess it's relatively rare that a gem would (intenti... -
- ko1 (Koichi Sasada) wrote in #note-13:
> if lits contains Ruby expression, SyntaxError
Could you give an example?
SyntaxError doesn't seem OK to me. It should simply not freeze if not a literal. -
- ko1 (Koichi Sasada) wrote in #note-12:
> * It is possible to break other library easily:
That sounds very bad code breaking the encapsulation of that other library.
Of course, no gems should directly mutate constants of another gem.... -
- By discussing with Matz and several MRI committers, we decided to introduce conservative option and radical option as experimental.
* the name of pragma is `shareable_constant_value` because it affects values referred from constants (... -
- `Ractor.make_shareable` does traverse reachable and not-already-shareable objects for other objects than Procs, it seems bad that it behaves differently for Proc.
I think the intention is clear with `Ractor.make_shareable(Proc.new{p a})... -
- Applied in changeset commit:git|5d97bdc2dcb835c877010daa033cc2b1dfeb86d6.
----------
Ractor.make_shareable(a_proc)
Ractor.make_shareable() supports Proc object if
(1) a Proc only read outer local variables (no assignments)
(2) read out... -
- By discussion with Matz and several MRI committers, we decided that making shareable Proc should be more conservative.
* `Ractor.make_shareable(read_values)` should be danger to freeze objects unexpectedly.
* if all read variables are s... -
- @hsbt there was no response to https://bugs.ruby-lang.org/issues/16778#note-22
How about reopening this issue?
@deivid Are you still interested to do that PoC for a single default gem?
I think it would be helpful to make progress on... -
- >Now after the recent positive comments you changed the status to "rejected". Could you clarify?
It's my mistake.
But no one submit a patch for this issue while 6 months. I reject this. -
- Ractor.make_shareable() supports Proc object if
(1) a Proc only read outer local variables (no assignments)
(2) read outer local variables are shareable.
Read local variables are stored in a snapshot, so after making
shareable Proc, any... -
-
04:23 PM Feature #16670: Reverse order of `expression` in `pattern` for 1-line pattern matching while it's still experimental
- There were notes in the recent dev meeting that affect this issue: https://github.com/ruby/dev-meeting-log/blob/master/DevelopersMeeting20201026Japan.md#feature-17260-promote-pattern-matching-to-official-feature-ktsj
`=>` is a new fea... -
- marcandre (Marc-Andre Lafortune) wrote in #note-8:
> How about:
> ...
Matz, how about this proposal?
-
- commit:7ad56fd87b35abf4933e0146761df91e9ec9890a
-
- commit:1c6ebe14fbdb2bc23878133cbf7a99ea856e3d89
-
- Applied in changeset commit:git|c0aeb98aa903334f06758d39c772cb22440d8a4e.
----------
Make ENV.replace handle multiple environ entries with the same key
While it is expected that all environment keys are unique, that is
not enforced. It... - 03:09 PM Revision 502d6d84 (git): * 2020-10-30 [ci skip]
-
- While it is expected that all environment keys are unique, that is
not enforced. It is possible by manipulating environ directly you
can call a process with an environment with duplicate keys. If
ENV.replace was passed a hash with a key... -
- Isolated Proc prohibit to access outer local variables, but it was
violated by binding and so on, so they should be error. -
- It would replace "C:/MSYS64/..." as "/C/MSYS64/...".
Where did a slash go? -
06:34 AM Bug #16651: Extensions Do Not Compile on Mingw64 with mingw32-make
- This is still and issue with Ruby 2.7.2.
The offending line of code is now at line 1908 in mkmf.rb.
-
-
06:26 AM Feature #17292: Hash Shorthand / Punning
- I would agree this is a duplicate, but in the last year we have had the introduction of the pattern matching syntax which makes this less of a syntactical oddity than it may have been in the past.
-
- ### Set Literal vs Javascript Object Punning
There was a proposal for a Set literal here: https://bugs.ruby-lang.org/issues/16989
```ruby
set = { 1, 2, 3 }
```
...but it was brought up that this is similar to the Javascript Ob... -
05:50 AM Bug #17142: Ruby fails to build in AIX
- Are you using GCC to build ruby? What was the error you hit?
-
- Applied at commit:ba889100d850e973e519cebc48d5b4f1e8ab0034
-
- I would concur with Marc-Andre on this one, I believe punning would be a more valuable feature, especially for keyword arguments.
Examples:
```ruby
def method_name(foo: 1, bar: 2, baz: 3)
foo + bar + baz
end
foo = 1
bar = 2
baz = 3
... -
- I'm personally hoping that `strip: ` could be syntax sugar for `strip: strip`...
-
02:54 AM Feature #17290 (Closed): Syntax sugar for boolean keyword argument
- We frequently use keyword arguments just to pass `true` value out of the truthy/falsy options given. And in many such cases, the falsy option is set as the default, and only the truthy value is ever passed explicitly. I propose to have a...
-
03:05 AM Feature #17291 (Assigned): Optimize __send__ call
- I made a patch to optimize a `__send__` call. This optimization replaces a `__send__` method call with a call of the method whose name is the first argument of `__send__` method. The patch is available in [this pull-request](https://gith...
-
- Let me tell you that I currently have no idea what is going on. If `rb_funcall` is broken the situation must be more catastrophic than what is reported here (happens once a day).
-
- This way the header flags and object internals are set correctly
10/28/2020
-
- It's not necessary to check ivpt because objects are allocated as
"embedded" by default -
- I've added a pull request to fix this, though I don't have the ability to test on AIX: https://github.com/ruby/ruby/pull/3717
-
10:43 PM Feature #17206: Introduce new Regexp option to avoid global MatchData allocations
- Sorry. “a huge amount of String garbage” is my misunderstanding.
But I don’t know under what situation this option may cause a bug.
-
-
-
- Applied in changeset commit:git|dfb3605bbee9c3cfbc1c354594c367472f29cb35.
----------
Add Thread.ignore_deadlock accessor
Setting this to true disables the deadlock detector. It should
only be used in cases where the deadlock could be ... -
- Setting this to true disables the deadlock detector. It should
only be used in cases where the deadlock could be broken via some
external means, such as via a signal.
Now that $SAFE is no longer used, replace the safe_level_ VM flag
wi... -
08:59 PM Feature #17288: Optimize __send__ call with a literal method name
- Just a few things:
We need to also remember **.instance_variable_get()** and **.instance_variable_set()**.
Ruby does not quite use a similar "restriction-style" OOP like, say, java. It will
depend a lot on the style and preferences of ... -
- shyouhei (Shyouhei Urabe) wrote in #note-4:
> Private methods shall not be called at the first place. Period. That is breaking encapsulation.
I wish that was the case, but Ruby access is *not expressive enough* for this to be the cas... -
- Eregon (Benoit Daloze) wrote in #note-5:
> Here are the first 1000 .send() usages in gems:
> ...
So? I don’t think we should follow that. If people misunderstand what an OOPL is, we would better not confirm that.
> > Private method... -
- Here are the first 1000 .send() usages in gems:
https://gist.github.com/eregon/21c8f14c478089c1a9295c21661583a9
420 of them use a literal Symbol for the first argument.
> Private methods shall not be called at the first place. Perio... -
- zverok (Victor Shepelev) wrote in #note-3:
> @shyouhei what about private methods?
Private methods shall not be called at the first place. Period. That is breaking encapsulation.
Again I’m not against the ability to do such things... -
08:34 AM Feature #17288: Optimize __send__ call with a literal method name
- @shyouhei what about private methods?
-
- Hello, I'm against this optimisation. `obj.__send__(:method)` should just be written as `obj.method`.
Not against the ability to write `obj.__send__(:method)`, but `obj.method` must be the preferable way and thus must be the fastest ... -
- I think it would be nice to make it its own gem (`tvar` maybe?) given it's under `Thread` and not under `Ractor`, and it could most likely work on other Ruby implementations (e.g., TruffleRuby).
That should also make it possible to e.g.... -
- I wrote a long-form blog post to give people interested in this proposed feature some context.
https://chrisseaton.com/truffleruby/ruby-stm/
I've also suggested a benchmark that we can start to use for experimenting. -
- Same as 5be42c1ef4f7ed0a8004cad750a9ce61869bd768
-
- As of 0b81a484f3453082d28a48968a063fd907daa5b5, `ROBJECT_IVPTR` will
always return a value, so we don't need to test whether or not we got
one. T_OBJECTs always come to life as embedded objects, so they will
return an ivptr, and when th... -
- We don't need to check the existence if an ivptr because non-embedded
objects will always have one - 03:42 PM Revision 9190451f (git): * 2020-10-29 [ci skip]
-
- 01:12 PM Revision 93e6364a (git): merge revision(s): 07786ed
- * test/net/http/test_https.rb: Stop the error due to openssl 1.1.1h
On some environments that uses OpenSSL 1.1.1h, the two tests now fail.
http://rubyci.s3.amazonaws.com/android29-x86_64/ruby-master/log/20200924T062352Z... -
- mame (Yusuke Endoh) wrote in #note-5:
> Okay, I'll add it.
Thanks.
> ...
I think it's not a big issue if TypeProf is meant only as a CLI/standalone tool, and not a gem to `require` at runtime.
Then people can generate .rbs files ... -
- > maybe still ship it but raise a nice error if used on RUBY_ENGINE != "ruby"?
Okay, I'll add it.
> ...
Sorry. In (far) future, I'd like to improve TypeProf to use AST instead of bytecodes if this project is considered successful. ... -
-
- Looking at it. Though I cannot reproduce this either.
mame (Yusuke Endoh) wrote in #note-2:
> This falls back to `rb_funcall`. This `rb_funcall` is replaced with `rb_funcallv_with_cc`. This should call FIXNUM's plus, but it seems ... - 01:22 AM Revision fb3c711d (git): compile.c: separate compile_builtin_function_call (#3711)
-