[#90399] [Ruby trunk Feature#14813] [PATCH] gc.c: make gc_enter+gc_exit pairs dtrace probes, too — ko1@...
Issue #14813 has been updated by ko1 (Koichi Sasada).
3 messages
2018/12/10
[#90417] [Ruby trunk Bug#15398] TestThread#test_signal_at_join fails on FreeBSD — naruse@...
Issue #15398 has been reported by naruse (Yui NARUSE).
4 messages
2018/12/11
[#90423] Re: [Ruby trunk Bug#15398] TestThread#test_signal_at_join fails on FreeBSD
— Eric Wong <normalperson@...>
2018/12/11
[email protected] wrote:
[#90519] Spoofing warnings for mail from bugs.ruby-lang.org — Charles Oliver Nutter <headius@...>
I'm getting a spoofing warning for emails sent from bugs.ruby-lang.org when
4 messages
2018/12/13
[#90522] Re: Spoofing warnings for mail from bugs.ruby-lang.org
— Eric Wong <normalperson@...>
2018/12/13
Charles Oliver Nutter <[email protected]> wrote:
[#90533] [Ruby trunk Feature#15413] unmarkable C stack (3rd stack) — normalperson@...
Issue #15413 has been reported by normalperson (Eric Wong).
3 messages
2018/12/14
[#90581] [Ruby trunk Bug#15424] Ruby 2.6.0rc1 & 2.6.0rc2 mutex exception — mat999@...
Issue #15424 has been reported by splitice (Mathew Heard).
3 messages
2018/12/17
[#90595] [Ruby trunk Bug#15430] test_fork_while_parent_locked is failing status on Ruby CI — hsbt@...
Issue #15430 has been reported by hsbt (Hiroshi SHIBATA).
3 messages
2018/12/18
[#90614] [Ruby trunk Bug#15430][Assigned] test_fork_while_parent_locked is failing status on Ruby CI — hsbt@...
Issue #15430 has been updated by hsbt (Hiroshi SHIBATA).
4 messages
2018/12/19
[#90630] Re: [Ruby trunk Bug#15430][Assigned] test_fork_while_parent_locked is failing status on Ruby CI
— Eric Wong <normalperson@...>
2018/12/20
> It still exists. https://rubyci.org/logs/rubyci.s3.amazonaws.com/centos7/ruby-trunk/log/20181218T230003Z.fail.html.gz
[#90820] Re: [ruby-cvs:73697] k0kubun:r66593 (trunk): accept_nonblock_spec.rb: skip spurious failure — Eric Wong <normalperson@...>
[email protected] wrote:
3 messages
2018/12/30
[ruby-core:90836] [Ruby trunk Feature#10548] remove callcc (Callcc is now going obsoleted. Please use Fiber.)
From:
fg@...
Date:
2018-12-31 11:28:48 UTC
List:
ruby-core #90836
Issue #10548 has been updated by decuplet (Nikita Shilnikov).
FWIW, I do have a practical example for `callcc` which cannot be implemented with fibers, or at least I don't see the way it could.
I'm the author of the [dry-monads](https://github.com/dry-rb/dry-monads/) gem. Along with a bunch of monads it provides an emulation of Haskell's do notation:
```ruby
class Operation
include Dry::Monads::Result::Mixin
include Dry::Monads::Do
def call(monadic_value)
extracted_value = yield monadic_value
# ...
Success(extracted_value + 1)
end
end
```
Here if `monadic_value` is `Success(value)` then `yield` will extract `value` from it and continue the execution. And if `monadic_value` is `Failure(...)` it will halt the execution and return this `Failure` as a result of `call`. Everything works perfectly fine and allows writing robust production code but only for monads that wrap 1 value inside. That is, it doesn't work for the list monad:
```ruby
class Operation
include Dry::Monads::Do
include Dry::Monads::List::Mixin
def call
v = yield List[1, 2, 3]
List[v + 1]
end
end
```
^this will return `List[2]` rather than `List[2, 3, 4]`. In order to make it work as expected, I would need to capture the continuation within `yield` so it can continue `call` more than once. I tested it, and it indeed works, but I don't want to depend on a to-be-removed feature.
----------------------------------------
Feature #10548: remove callcc (Callcc is now going obsoleted. Please use Fiber.)
https://bugs.ruby-lang.org/issues/10548#change-76019
* Author: tarui (Masaya Tarui)
* Status: Open
* Priority: Normal
* Assignee:
* Target version:
----------------------------------------
We are paying a lot of costs for callcc's consistency.
and currently, we can use Fiber in many situation.
In https://bugs.ruby-lang.org/projects/ruby/wiki/DevelopersMeeting20140517Japan,
matz agreed to remove callcc.
If there is no refutation, remove callcc in the future version.
--
https://bugs.ruby-lang.org/
Unsubscribe: <mailto:[email protected]?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>