Activity
From 10/23/2019 to 10/29/2019
10/29/2019
-
11:25 PM Revision c54635c0 (git): Update Unicode Emoji version from 12.0 to 12.1.
- This update does not add any new codepoint assignments, it just
expands the range of emoji codepoint sequences recommended for
public interchange.
Depending on how emoji data files are cached, this commit may
require manual intervention... -
09:51 PM Feature #16276: For consideration: "private do...end" / "protected do...end"
- Eregon (Benoit Daloze) wrote:
> Also worth noting that `private def` actually defines two methods, one public and then a copy of it as private, overriding the public one in the method table.
I don't think this is true. `private :met... -
09:17 PM Feature #16276: For consideration: "private do...end" / "protected do...end"
- I kind of like this idea as it would make it clear which methods are private by indentation.
`private` alone is indeed hard to notice as soon as there are a few methods in the class.
OTOH, using this to change a method from private t... -
08:38 PM Feature #16276: For consideration: "private do...end" / "protected do...end"
- shevegen (Robert A. Heiler) wrote:
> > As noted in the pseudocode above, we can clean up some of the issues around
> ...
Agree with all you said and appreciate the detailed feedback - but on this, and in many ways on the use of `send... -
- This looks like the Mac OS getaddrinfo bug. See the part of the C-level backtrace before the crash:
```
/usr/lib/system/libsystem_platform.dylib(_sigtramp+0x1d) [0x7fff7cbf8b5d]
/usr/lib/system/libsystem_trace.dylib(_os_log_preferen... -
09:42 AM Bug #16283: A fork in transaction of PG cause Segmentation fault
- Pretty sure that's the OSX specific bug that got fixed in 2.6.4 or 2.6.5 (This one IIRC but I might be wrong https://bugs.ruby-lang.org/issues/15887).
Can you try with 2.6.5 ? -
03:55 AM Bug #16283 (Third Party's Issue): A fork in transaction of PG cause Segmentation fault
- Call Kernel#fork in transaction of Postgres and call some Socket method in fork's block, then ruby on the child process abort with segmentation fault.
Conceptual code:
```
MGModel.connection.transaction do
# Do something
... - 03:14 PM Revision 92c13380 (git): * 2019-10-30 [ci skip]
-
03:13 PM Revision 22dbbbeb (git): Compacting the heap can cause GC, so disable it
- When we compact the heap, various st tables are updated, particularly
the table that contains the object id map. Updating an st table can
cause a GC to occur, and we need to prevent any GC from happening while
moving or updating referen... -
01:40 PM Revision fee5cde0 (git): Fix tests for CVE-2018-6914
- Since the current working directory is not involved in `Tempfile`
and `Dir.mktmpdir` (except for the last resort), it is incorrect
to derive the traversal path from it. Also, since the rubyspec
temporary directory is created under the b... -
11:05 AM Feature #16275: Revert `.:` syntax
- Jeremy – I’m sorry for the overreach in that clumsy wording. Let me rephrase: what I saw here was a fair number of comments supporting the removal of an already-implemented feature of 2.7 that I felt had good potential and that I was per...
-
-
07:05 AM Revision 9195ed18 (git): Revert "Check for nonnull attribute in configure"
- This reverts commit 54eb51d72bc43f90b595f0d7ffb5069ebf1a56d9.
Windows build failure. See also https://github.com/ruby/ruby/runs/278718805 -
05:40 AM Revision 7bf51ced (git): test/rubygems/test_gem.rb: early failure when there is /tmp/Gemfile
- Some test cases in rubygems assume that /tmp/Gemfile does not exist.
If it does, they fail with very difficult-to-understand message:
```
[ 149/2108] TestGemBundlerVersionFinder#test_bundler_version_with_bundle_update_bundler = 0.00
1... -
- This reverts commit ca5812fe4516a10cc687281f9e47e1a08449f1ab.
Now tool/lib/minitest provides "omit", so it should work. -
- According to rdoc, test-unit provides omit instead of skip.
This is a compatibility layer to make it work with both test-unit and
tool/lib/minitest. -
- This reverts commit b4da6fc1c277190bbd10e795ebf3be45772038e8.
`make test-all` uses minitest, which led to "undefined method `omit'" -
03:34 AM Revision 9525541d (git): [ruby/rdoc] Use Dir.glob to convert short path of Dir.tmpdir to long path
- https://github.com/ruby/rdoc/commit/ba16e44572
-
- https://github.com/ruby/rdoc/commit/946d2592e2
-
- https://github.com/ruby/rdoc/commit/1c5bf2ae1d
-
-
03:07 AM Revision b86e5c9f (git): Clang can also use C call cache
- Previously this was restricted to only gcc because of the
GCC_VERSION_SINCE check (which explicitly excludes clang).
GCC 3.3.0 is quite old so I feel relatively safe assuming that all
reasonable versions of clang support this. -
02:32 AM Revision 85b88c1d (git): Let the arrays for the singleton and instance method reflection helpers be initialized to the methods count
-
-
-
-
-
-
-
- Actually, I think this makes performance worse because it removes the "define". So there will be only one. I will fix it to maintain the macro.
10/28/2019
-
-
- Hi,
Currently the compactor will invalidate all inline caches. I would like to update references in inline caches so we don't have to invalidate. Most inline caches are reachable from instruction sequences, but one cache is not:
... -
- This reverts commit 60a7f9f446604571f8a81499080c57c47baf0e6b.
We can't have Ruby objects pointing at T_ZOMBIE objects otherwise we get
an error in the GC. We need to find a different way to update
references. -
- When we run finalizers we have to copy all of the finalizers to a new
data structure because a finalizer could add another finalizer and we
need to keep draining the "real" finalizer table until it's empty.
We don't want Ruby programs to... -
-
- We need to ensure that labels are pinned while disassembling. If the
compactor runs during disassembly, references to these labels could go
bad, so this commit just ensures that the labels can't move until we're
done. -
- 06:19 PM Revision a51583b6 (git): * 2019-10-29 [ci skip]
-
-
-
- > What about rb_str_fstring_lookup and rb_str_fstring_lookup_enc?
I don't think a lookup would be enough for what I'd like to do.
A typical use case would be a JSON document with lots of duplicated strings.
If we only lookup t... -
-
-
07:53 AM Revision 3e83f1f0 (git): Add more matrix info to slack payload
-
- Test included for the situation formerly was not working.
- 03:20 AM Revision a72cb6b1 (git): * 2019-10-28 [ci skip]
-
03:19 AM Revision d8d581bf (git): add assertion for mutex_lock.
- After do_mutex_lock(mutex), the mutex should be owned by the current
thread. Adding an assertion for this assumption.
10/27/2019
-
- Attached is a patch with a test for fixing this.
-
- Fixed in commit:afd68cd87114fb49158462f1594cacfd2b765e9b.
-
-
- Pull request submitted to fix this: https://github.com/ruby/reline/pull/62
-
08:41 PM Bug #16278: Potential memory leak when an hash is used as a key for another hash
- Thanks both @jeremyevans0 @alanwu for the rich and clear explanations!
-
-
10:45 AM Feature #14145: Proposal: Better Method#inspect
- This PR provides method parameters inspect: https://github.com/ruby/ruby/pull/2618
Implementation is most probably not optimal (to say the least), I am ready to fix it by comments. At least the tests and implementation should handle all... -
- I want to expand on my semantics concern, for the performance concern I should get some numbers first.
jeremyevans0 (Jeremy Evans) wrote:
> Technically, `**hash` automatically converts a positional hash to keywords. So I definitely ... -
- * Add to NEWS;
* Add examples of while-alike cycles with practical tasks. -
01:41 AM Revision aba23d83 (git): Fix documentation for Fiber#transfer [ci skip]
- Fiber#transfer prevents calling Fiber#resume on the receiver of the
transfer method, not the fiber calling transfer.
Transfering back to a fiber does not allow later calling resume on
the fiber. Once transfer has been called on a fiber...
10/26/2019
-
- * Move Unicode changes under String / Unicode for consistency with the rest.
-
- There are PRs to fix those: https://github.com/rails/rails/pull/37504
-
-
- 05:24 PM Revision 9c5a9623 (git): * 2019-10-27 [ci skip]
-
- * Make links from Net::GenericHTTPRequest work;
* Document +dest+ param of HTTPResponse#read_body;
* Slightly improve reference to particular response
classes from HTTPResponse class docs. -
-
-
-
-
- * More explanations/examples in class docs;
* Fix links to other methods (remove -
- * Actualize Notes about other templating engines;
* Document #location= method. -
04:31 PM Bug #16278: Potential memory leak when an hash is used as a key for another hash
- The GC scans the native stack for Ruby's C code to find values to retain.
Pointers to Ruby's heap objects can end up on the native stack for a variety
of reasons, and this is mostly up to the C compiler. Whether a pointer ends up
on t... -
- cristiangreco (Cristian Greco) wrote:
> Hi Jeremy, thanks for these details!
> ...
It is eventually collected when Ruby's GC can no longer find a reference to it. The reason it may be retained even though there is no direct reference ... -
- Hi Jeremy, thanks for these details!
I don’t know the details of ruby’s GC, seems to me it might behave unpredictably sometimes. I guess what confuses me now is that although that object is retained we don’t observe unbounded memory g... -
- Adding this method and calling it after `create` clears the output.
```ruby
def garbage
h1 = h2 = h3 = h4 = h5 = h6 = h7 = h8 = h9 = h10 = nil
end
```
So a “shadow” seems staying on the VM stack. -
- Here's a modified version of your script, fixing the issue where `$id_h4 = h3.object_id`, and showing the actual contents of the objects found with those ids:
```ruby
require 'objspace'
class Klass; end
def create
h1 = { :a ... -
- (Sorry for being over-active. On the bright side, it could be a final bunch from me)
Carry-over from tickets with feedback:
* [Feature #16122] `Struct::Value`: simple immutable value object. First version of the proposal was not clea... -
12:09 PM Feature #16275: Revert `.:` syntax
- > with several core team members agreeing on this
At the end of the day you only need to find pro/con arguments for matz. :)
Once a syntax is picked, though, it may be mutually exclusive to other syntax
and follow-up ideas buildin... -
- zverok (Victor Shepelev) wrote:
> OK, with several core team members agreeing on this (and even PR prepared), I believe this is already a lost cause, but I'd still like to put some perspective here, if just for reference and future disc... -
- timriley (Tim Riley) wrote:
> I’m opposed to this reversion. I was looking forward to using `.:` in 2.7. I felt I should say this as a representative of perhaps a “silent majority” of Ruby users.
If you think your opinion represents... -
02:44 AM Feature #16275: Revert `.:` syntax
- matz (Yukihiro Matsumoto) wrote:
> I am for adding syntax sugar for method reference. But I don't like proposed syntax (e.g. ->).
> ...
So clearly the syntax sugar for method reference is something that we *will* have. Eventually if no... -
- https://github.com/bundler/bundler/pull/7394
-
09:09 AM Bug #8855: {Single}Forwardable#def_delegators が、Stringでメソッド名を渡された時だけ __id__ と __send__ が取り除かれる
- merged into ruby core at d00551a7bb1d5dbabb0a8c95d6bd2d9d4e86934a
-
-
-
- For readability. Requested by ko1.
See: https://github.com/ruby/ruby/commit/356e203a3acd4d3d20ba12f956fd22e17b6363e9#r35661401 -
- * Top-level `return`;
* Documentation for comments syntax;
* `rescue` inside blocks;
* Enhance `Object#to_enum` docs;
* Make `chomp:` option more obvious for `String#each_line` and
`#lines`;
* Enhance `Proc#>>` and `#<<` docs;
* Enhanc... -
- Raises an error on end-exclusive ranges unless endless, regardless
the receiver. -
12:26 AM Revision f14b7541 (git): [ruby/forwardable] Use Gemfile instead of Gem::Specification#add_development_dependency.
- https://github.com/ruby/forwardable/commit/1e7123a81b
-
- https://github.com/ruby/forwardable/runs/242918994#step:5:12
```
Error: test_obj_single_delegators_send_id(TestForwardable): NoMethodError: private method `attr_reader' called for #<Class:#<Object:0x00005605af501f58>>
```
https://github... -
- https://github.com/ruby/forwardable/commit/1a994c90e1
-
- Previously, __send__ and __id__ were skipped if provided as strings,
but not skipped if provided as symbols.
Fixes Ruby Bug 8855.
https://github.com/ruby/forwardable/commit/2e61c8c66c -
- https://github.com/ruby/forwardable/commit/1b6991e589
-
- https://github.com/ruby/forwardable/commit/387758d45a
10/25/2019
-
- I’m opposed to this reversion. I was looking forward to using `.:` in 2.7. I felt I should say this as a representative of perhaps a “silent majority” of Ruby users.
I think that some of the additional ideas this feature was spawning... -
- @zverok I really feel your pain, I had the same reaction when some of my ideas were ignored or rejected; that never feels good, especially so if you strongly believe to be right. Just take a bit of distance, don't take it personally, rem...
-
- OK, with several core team members agreeing on this (and even PR prepared), I believe this is already a lost cause, but I'd still like to put some perspective here, if just for reference and future discussion.
> Disclaimer: This matte... -
- jeremyevans0 (Jeremy Evans) wrote:
> `object_id` is only unique for the life of the object. After the object is garbage collected, the same `object_id` could be used for a different object. So measuring using `object_id` is not a go... -
- cristiangreco (Cristian Greco) wrote:
> Using each store I found that the 3 labels hashes are retained after garbage collection (all the stores use a similar pattern of storing labels hashes within another hash).
> ...
`object_id` is o... -
- ko1 (Koichi Sasada) wrote:
> > If an application exercises this pattern very frequently during lifetime and across multiple processes then it’s definitely going to bloat memory, at the very least. As a real-world example, this is causin... -
- > If an application exercises this pattern very frequently during lifetime and across multiple processes then it’s definitely going to bloat memory, at the very least. As a real-world example, this is causing high memory usage for the Pr...
-
- Ruby 2.7 deprecates taint and it no longer has an effect.
The lack of taint support should not cause a problem in
previous Ruby versions.
https://github.com/ruby/dbm/commit/1f0ff0bce1 -
08:39 PM Bug #16281 (Closed): `irb -w` issues warning
- ```
$ irb -w
.rvm/rubies/ruby-head/lib/ruby/2.7.0/reline.rb:322: warning: instance variable @ambiguous_width not initialized
```
(Since f13db4adde532) -
- I find the documentation clear, and all three classes include mixed examples as in your example above.
-
- 05:56 PM Revision 41d52945 (git): * 2019-10-26 [ci skip]
-
- Revert 46f175ed5c8560b3c9da5ab7b4fa73287f1eb1c5 partially.
Also tool/ruby_vm scripts refer the options in vm_opts.h. -
03:39 PM Bug #16277: UNIXServer#listen fails with Errno::EADDRINUSE error under Windows 10 / WSL Ubuntu 18.04
- Would something like the following yield an equivalent object?
```ruby
require 'socket'
sock = Socket.new :UNIX, :STREAM
sock.bind Addrinfo.unix('tmp.sock', :STREAM)
sock.listen 1024
puts sock.local_address.unix?
``` -
- Allows a beginless/endless range, and an end-exclusive range
unless the receiver is smaller than its end. -
- > 1.clamp(0...3) #=> 1
> ...
I don't think it's a good idea for the error to depend on the value being clamped. When Matz said "It should raise an error on end-exclusive ranges" I'm pretty sure it was supposed to mean a simple argument ... -
- Sounds reasonable, and matz says “an error on end-exclusive ranges” at https://bugs.ruby-lang.org/issues/14784#change-81254 and ditto in the log of 20190829 dev meeting, but nothing about beginless/endless ranges.
Seems I had been confu... -
- @nobu is there any chance you can reconsider your implementation?
The important justification for the proposal was using `#clamp` with open ranges (begin- and end-less), but your implementation just rejects them all (with misleading e... -
- Perhaps, it is an issue of sassc. Could you please ask them first?
I'm unsure but it looks related to https://github.com/sass/sassc-ruby/issues/146 -
10:13 AM Bug #16280 (Third Party's Issue): FFI Illegal instruction
- After calling bundle exec rails c -e production I'm getting the following output:
../bundle/ruby/2.5.0/gems/ffi-1.11.1/lib/ffi/library.rb:112: [BUG] Illegal instruction at 0x00007f76fa252980
ruby 2.5.1p57 (2018-03-29 revision 63029) ... -
- http://ci.rvm.jp/results/trunk-vm-asserts@silicon-docker/2340856
-
- These tests rely on GC.stat and GC.last_gc_info, which are not
stable when GC.stress is true. Skip them for that case. -
-
06:53 AM Bug #16236: Cannot handle logrotate on Windows when one file is written from multi process/thread
- Fluentd side patch: https://github.com/fluent/fluentd/pull/2663
Fluentd side issue: https://github.com/fluent/fluentd/issues/2446 -
- Thanks for the information.
This issue should be Fluentd logging mechanism issue not Ruby core logger library.
Fluentd side logrotate issue is fixed.
So, it can be closed. -
-
03:32 AM Bug #16279 (Closed): Backport 463092b8
- Please backport the rake 12.3.3 update into the stable releases
rev: 463092b84da7933f307cc8747f948f68ef19f5fd
This patch resolves a public disclosed minor security issue: https://hackerone.com/reports/651518
And causes the curr... -
- Replacing adjacent struct rb_call_info and struct rb_call_cache
into a struct rb_call_data. -
02:10 AM Bug #16161 (Closed): tailcall_optimization may be disabled after r67315
- Thank you to merge https://github.com/ruby/ruby/pull/2529 on 4ff2c58f919153b9a47f69f855a0b9d2bb0e0bbe.
I confirmed this issue is fixed now.
```
$ ./miniruby -v -e 'iseq = RubyVM::InstructionSequence.compile("def foo(n, s = 0);return... -
- Use cmd instead of new default shell for `call`.
https://github.blog/changelog/2019-10-17-github-actions-default-shell-on-windows-runners-is-changing-to-powershell/
https://github.com/ruby/ruby/commit/7bcc639c720b59eb2199601963bcfa72016... -
-
- https://github.com/ruby/tracer/commit/9df7d7937b
-
- Previously, the keyword hash was duped (which results in a regular
hash), but the dup was not marked as a keyword hash, causing the
hash not to be marked as keyword hash even though it should be.
10/24/2019
-
-
- Eregon (Benoit Daloze) wrote:
> jeremyevans0 (Jeremy Evans) wrote:
> ...
As we discussed, here is a link to the benchmark: https://pastebin.com/raw/inwr6GvW
You'll want to compare the master branch with a branch that removes `ruby2_... -
- Sorry, f62f90367fc3bce6714e7c34cbd040e14e43fe07 is push miss.
-
- `param.flags.ruby2_keywords` is not store/load correctly at to_binary
so restore this flag correctly. -
- This mirrors the behavior when manually splatting a hash. This
mirrors the changes made in setup_parameters_complex in
6081ddd6e6f2297862b3c7e898d28a76b8f9240b, so that splatting to a
non-iseq method works the same as splatting to an is... -
- Allow Date.new spec to run on 2.7.
Separate Date.valid_jd? specs, since 2.7 is now stricter and
requires numeric value for the first argument. -
- Add a test for this case.
-
- METHOD::klass can contain T_ICLASS so inspect should respect it.
-
06:45 PM Feature #16275: Revert `.:` syntax
- `p obj.:hoge` can output source location of `#hoge` (with [#14145](https://bugs.ruby-lang.org/issues/14145)).
```ruby
p obj.:hoge
# => #<Method: X#hoge ../ruby/test.rb:4>
```
I was looking forward to seeing this because it is ve... -
- mame (Yusuke Endoh) wrote:
> I'm currently thinking that the following design is preferable.
> ...
I agree with all the above. And if you can get Matz to reconsider #16120 nothing could make me happier :-)
But since I prefer `map(&:to... -
- +1 as well, it feels ad-hoc to me and rather not easy to read, and is less general than numbered parameters.
And it makes extra allocations of Method objects when there is no need. -
- > `?> erb`
`?>` is a character literal. -
01:33 AM Feature #16275: Revert `.:` syntax
- I've already fallen into using ` .:` in 2.7. I'd personally miss `.:` since it feels super natural to me.
-
- OpenSSL in chocolatey is 1.1.1d but outdated 1.0.2s is in vcpkg.
-
-
- PowerShell does not expand by `%varname%` syntax.
-
- Github workflow stopped using cmd.exe suddenly, and `||` and `&&`
seem not working in PowerShell. -
- Get rid of these redundant and useless warnings.
```
$ ruby -e 'def bar(a) a; end; def foo(...) bar(...) end; foo({})'
-e:1: warning: The last argument is used as the keyword parameter
-e:1: warning: for `foo' defined here
-e:1: warning... -
-
-
- 03:16 PM Revision 2ea69896 (git): * 2019-10-25 [ci skip]
-
-
- This is fixed by commit:1fb4584825.
-
- Fixes Ruby Bug 9876.
-
- So that the result structure can be accessed as `$number`
variables, not a mere `VALUE`. -
- This reverts commit 5ebb0d50f6560b35bc03deb79341a115c5f782ee.
-
- This reverts commit 4d844cbaed518743776594fa5ae33b86fe176ad1.
-
- This reverts commit ce6caade7c57a505f73086ccd7b33c14f7715f22.
-
- Only untaint result on Ruby <2.7, as taint support is deprecated
in Ruby 2.7+ and no longer has an effect.
https://github.com/ruby/webrick/commit/4c430f9410 -
- https://github.com/ruby/webrick/commit/6b6990ec81
-
- While the stripping of header values is required by RFC 2616 4.2 and
RFC 7230 3.2.4, the squishing is not and can break things, such as
when one header contains an HMAC of another header.
Fixes Ruby Bug 7021.
https://github.com/ruby/we... -
- https://github.com/ruby/webrick/commit/00c281caa7
-
- It is currently broken, and even if it worked, it can cause problems
when debugging. See Ruby Bug 10715.
https://github.com/ruby/webrick/commit/575dea8656 -
10:46 AM Revision f0452574 (git): [ruby/webrick] after ruby-2.6.0, set Net::HTTP#write_timeout
- https://github.com/ruby/webrick/commit/3b51f6b4d2
-
- Ruby 2.7 deprecates taint and it no longer has an effect.
The lack of taint support should not cause a problem in
previous Ruby versions.
https://github.com/ruby/fiddle/commit/18d6fb6915 -
10:34 AM Revision ce6caade (git): [ruby/fiddle] Use ffi_closure_free by default. (#20)
- * Use ffi_closure_free unconditionally.
The current conditionals reflect historic heritage of FFI. Usage of
ffi_closure_free should be better default nowadays, because libffi 3.0.5
fixing issues of ffi_closure_free should be widely avai... -
- https://github.com/ruby/fiddle/commit/ea06b28db8
- 10:34 AM Revision 4d844cba (git): [ruby/fiddle] test: use env Hash
- https://github.com/ruby/fiddle/commit/a01a962342
- 10:34 AM Revision 5ebb0d50 (git): [ruby/fiddle] Fix a failing test (#13)
- * Fix a failing test
This commit fixes the following failure:
```
1) Failure:
Fiddle::TestImport#test_no_message_with_debug [/Users/mrkn/src/github.com/ruby/fiddle/test/fiddle/test_import.rb:152]:
1. [2/2] Assertion for "stderr"
... - 10:34 AM Revision 7733db66 (git): [ruby/fiddle] Fiddle::Function must maintain a reference to the closure
- If the first parameter to Fiddle::Function is a closure object (rather
than an interger), `rb_Integer` will cast it to an integer but not
maintain a reference to the closure. Then if the closure gets GC'd, we
have a segv. This commit k... -
-
- https://github.com/ruby/date/commit/13c94362c2
-
- https://github.com/ruby/date/commit/8c02586a98
-
- https://github.com/ruby/date/commit/af01edd7d8
-
- Ruby 2.7 deprecates taint and it no longer has an effect.
The lack of taint support should not cause a problem in
previous versions.
https://github.com/ruby/date/commit/519470dc3b -
- Fixes Ruby Bug 12961
https://github.com/ruby/date/commit/7f533c2552 -
- Previously, the type of these arguments were not checked, leading to
NoMethodErrors in some cases, and TypeErrors in other cases, but not
showing what field was having the problems. This change makes it so
the field with the problem is ... -
- Previously, julian dates would not round trip through to_time.to_date,
because Time is always considered gregorian. This converts the Date
instance from julian to gregorian before converting to Time, ensuring
that an equal date object w... -
- Applied in changeset commit:git|89e7997622038f82115f34dbb4ea382e02bed163.
----------
Combine call info and cache to speed up method invocation
To perform a regular method call, the VM needs two structs,
`rb_call_info` and `rb_call_cach... -
-
- To perform a regular method call, the VM needs two structs,
`rb_call_info` and `rb_call_cache`. At the moment, we allocate these two
structures in separate buffers. In the worst case, the CPU needs to read
4 cache lines to complete a met... -
- see https://bugs.ruby-lang.org/issues/9664#note-6
-
- The reported behavior is intentional.
Fibers are separated to two categories:
(1) Semi-coroutine: transition by resume/yiled. There is a "parent/child" relationship like function call (caller/callee).
(2) Coroutine: transition by ... -
- mame (Yusuke Endoh) wrote:
> This code uses constant memory. If it caused memory leak, the memory usage would continue to increase.
Thank for your answer!
If an application exercises this pattern very frequently during lifetime... -
- If a fiber is invoked with transfer method (such as "f.transfer"),
then the invoked fiber ("f") is labeled as "transferred" and this
fiber can not be invoked with Fiber#resume. This patch adds
transferred attribute for "Fiber#to_s" (and ... -
- This reverts commit fa8ac91e957a076f6df1adaecad7896817138009.
Previous behavior is intentional. -
- This reverts commit ff953a003e03f5f070112ececefab4c07ff4cb0e.
-
-
-
- FWIW, my personal style has evolved to using `private` inline:
```
class Foo
def public
end
private def some_private_instance_method
puts "I'm private"
end
private def also_some_private_instance_method
pu... -
- - C++: There are `private`, but no `private {}`
- Java: There are `private`, but no `private {}`
- Scala: There are `private`, but no `private {}`
- Kotlin: There are `private`, but no `private {}`
- Rust: Everything are private by d... -
- shevegen (Robert A. Heiler) wrote:
> Actually I should clarify some of my statements a bit more; I'll do it in a terse add-on.
> ...
This simply is sloppy coding.
> I believe in these cases, the suggestion here may possibly be of le... -
02:37 AM Bug #16251: Evaluation in binding differs from ruby execution
- This is a simpler example of the behavior:
```
$ ruby -e 'p x; x = 6'
Traceback (most recent call last):
-e:1:in `<main>': undefined local variable or method `x' for main:Object (NameError)
$ ruby -e 'p eval("x"); x = 6'
nil
$ r... -
- This is very nuanced. I'm not sure who is in charge of the exception.
`UNIXServer.new`'s return value socket is already listened inside of the method. Calling `listen` again on a socket that is already listening, might or might not ...
10/23/2019
-
- Ruby uses so-called conservative GC, which is inexact. It is not guaranteed that an object is collected when it becomes unreachable.
You can confirm that it does not cause leak by the following code:
```ruby
def create
h = {{:... -
- Hi,
I've been hitting what seems to be a memory leak.
When an hash is used as key for another hash, the former object will be retained even after multiple GC runs.
The following code snippet demonstrates how the hash `{:a => 1}`... -
- Coverity Scan complains it.
-
- +1 for the removal of `.:`.
> Originally it was to extract the exact method even if obj.method was overridden.
I think that it was just one of the motivations of that. Anyway, people will mainly (ab)use it like `.map(&JSON.:parse)... -
- I'm also in favor of removing `.:` until a better "whole picture" is formed. Besides, that syntax encourages the idea that symbols are closely related to functional objects. And it looks like cuneiform.
For example, if we consider tha... -
- I am in favor of removing `.:`. It was introduced before numbered parameters, but I think using numbered parameters is better than using `.:` for solving the same problems `.:` is designed to solve:
```ruby
%w'file1 file2'.map(&File... -
- Personally what I dislike about .: is mostly that I have to look carefully at the code
and think.
> It is not just for “the functional programming style”.
> ...
I think that the idea behind .: is ok but syntax-wise I am not sure if ... -
- Forgot the URL to revert: https://github.com/nobu/ruby/pull/new/feature/16275-revert-methref
-
- It is not just for “the functional programming style”.
Originally it was to extract the exact method even if `obj.method` was overridden. -
03:26 PM Feature #16275 (Closed): Revert `.:` syntax
- `obj.:method` is introduced at r66667 by #12125 and #13581.
It encourages the functional programming style in Ruby.
But this shorthand syntax is just for methods of `self` without arguments.
It causes another feature requests like #... -
- It made rdoc fail.
https://rubyci.org/logs/rubyci.s3.amazonaws.com/ubuntu1804/ruby-master/log/20191023T183005Z.fail.html.gz
```
RDoc is not a full Ruby parser and will fail when fed invalid ruby programs.
The internal error was:
... -
- Actually I should clarify some of my statements a bit more; I'll do it in a terse add-on.
- I believe that many ruby users may actually NOT indent when using private/public.
They may write code like this:
class Foo
... -
- In general I agree with the proposal, or at the least with the basic gist of it, e. g.:
private {
do_stuff
}
public {
do_stuff
}
I do not know how old private/public distinction is in ruby but I t... -
- Private or protected declarations in Ruby classes are problematic. The single, standalone `public`, `private` or `protected` statements cause all following methods - *except* "private" class methods, notably - to have that protection lev...
-
08:20 PM Bug #16277 (Closed): UNIXServer#listen fails with Errno::EADDRINUSE error under Windows 10 / WSL Ubuntu 18.04
- When running the following script under Windows 10 / WSL Ubuntu 18.04, an Errno::EADDRINUSE error is thrown. Expected result is that the script would run and simply exit.
``` ruby
#!/usr/bin/env ruby
# This script establishes a UN... -
- Personally I have had a need to transform keys (and values) in a hash quite a bit. We
also have strange thingies such as HashWithIndifferentAccess so that may be indicative
of people wondering about strings/symbols as keys for a hash i... -
- `String#gsub` also can take a block or a hash. Using a hash for `String#gsub` isn't possible in Perl or Python, but can be extremely handy. Maybe the behavior when there's both a block and a hash could be the same as for `String#gsub`?
-
09:20 AM Feature #16274: Transform hash keys by a hash
- shyouhei (Shyouhei Urabe) wrote:
> Understand the motivation (maybe that of #slice can be separated into another request).
> ...
Actually, I just came up with an additional idea regarding that exact point. Updated the issue. -
- Understand the motivation (maybe that of #slice can be separated into another request).
One quick question: what should happen if _both_ a block and an argument are passed at once? -
- We have `Hash#transform_keys` and its bang version to change the keys of a hash, but that requires passing a block, which assumes that the mapping from the old keys to the new keys follows some rule. But in reality, we frequently want to...
-
- Martin added this to the next developer meeting. I have not yet commented on
this issue so I may briefly do so.
matz asked back then between zip_with, or zip with symbol. I think zip_with may
be better than zip with symbol from a us... -
06:12 PM Revision df91896f (git): More rdoc for ENV#[] and ENV#fetch
-
05:59 PM Feature #14183: "Real" keyword argument
- The original intent seems to have been to separate named args from hashes and make them a distinct language feature with more consistent, easier to understand syntax and semantics. However, how does the following fit with that goal:
`... -
05:58 PM Feature #15198: Array#intersect?
- I tried setting that up here: https://github.com/ruby/ruby/pull/2598
I ignored infinite ranges for now -
- On German keyboard, right alt key acts as like shift key.
Ex. right-alt-8 is just "[". This input doesn't have meta-key statement. -
- Refreshes bundled gems to the latest version, and extracts them.
-
-
- jeremyevans0 (Jeremy Evans) wrote:
> You shouldn't even take your word, as you haven't implemented it yet. I'll post a benchmark, and I ask you to do the same.
Fair enough, I'll try to benchmark this soon in TruffleRuby then.
If I ... -
- @NuriYuri Thank you for your comment, but this ticket is not a good place to discuss it. Please add it to #14183 or create a new ticket.
-
- Eregon (Benoit Daloze) wrote:
> jeremyevans0 (Jeremy Evans) wrote:
> ...
As I stated last time, it's not that inefficient in CRuby. I'll try to benchmark to compare it tomorrow, but I expect it would make only a small difference in a ... -
- > is `.:hoge` a `:hoge.to_proc` syntax sugar?
No, and that's a core of the proposal. `:hoge.to_proc` produces regular `Proc` (which is different internally, but conceals this fact). `.:hoge` is meant to produce new core object.
> .... -
- Is `.:hoge` a `:hoge.to_proc` syntax sugar?
And, is `map(&self.:hoge)` and `map(&.:hoge)` different in meaning?
In Ruby, `self.hoge` and` hoge` without `self` often have the same meaning
But, it looks very strange that `map(&self.:hog... -
- Updated description significantly to clarify intentions.
-
- 03:00 PM Revision 659f7c0a (git): * 2019-10-24 [ci skip]
-
-
- Applied in changeset commit:git|1d91feaf13e0ffe04b2dabc6e77e4101b6d0bb07.
----------
Limit strict RUBY_METHOD_FUNC in C++
Limit strict function signature check with RUBY_METHOD_FUNC in C++
to bundled libraries only. [Bug #16271] -
- shyouhei (Shyouhei Urabe) wrote:
> So yes, the API change _revealed_ an arity mismatch here. `SWIG_ruby_failed` is getting more arguments than it expects, which is dangerous depending on machine ABI. It has to be fixed. I believe it'... -
- jeremyevans0 (Jeremy Evans) wrote:
> Attempting to build the taglib-ruby gem on ruby-2.7.0-preview2 fails with error messages such as:
> ...
Well, it seems the function called `SWIG_ruby_failed` is prototyped as `VALUE SWIG_ruby_failed... -
- Limit strict function signature check with RUBY_METHOD_FUNC in C++
to bundled libraries only. [Bug #16271] -
-
-
- Funnily enough (and not completely intentionally) the problem is "solved" with #16264:
```ruby
.:zip.call(*arrays)
# or even... for those who likes to cry "code golf!"
.:zip.(*arrays)
```
Currently, you also can
```ruby
:zip.to... -
07:12 AM Feature #16273: Proposal: Shorthand operator for "#instance_method"
- I don't think the first examples are messy.
On the contrary, the second examples using `bind_call` are quite messy than the first. -
- I don't think `Array.instance_method(:zip).bind_call(*arrays)` should be recommended, and worth adding shorthand operator.
-
- I don't think using `#` acceptable, and have thought `.::`.
-
- hi, created issues to discuss shorthand for "#instance_method"
## Overview
Ruby 2.7 adds a `#method` shorthand `.:` operator.
* [Feature #12125: Proposal: Shorthand operator for Object#method - Ruby master - Ruby Issue Tracking ... -
- @duerst
> What you want to do here is in many other languages done with `zip_with`
I used `zip` only as a simplest way to construct an example. In our current codebase we have a fare share of internal methods defined with two pairs... -
-
-
-