[#41916] Proposal: Bitmap Marking GC — Narihiro Nakamura <authornari@...>

Hi.

18 messages 2012/01/05

[#41941] [ruby-trunk - Bug #5851][Open] make check fails when compiling with GCC 4.7 - *** longjmp causes uninitialized stack frame *** — Vit Ondruch <v.ondruch@...>

12 messages 2012/01/06

[#41979] [ruby-trunk - Bug #5865][Open] Exception#== should return false if the classes differ — Hiro Asari <asari.ruby@...>

10 messages 2012/01/08

[#42003] [ruby-trunk - Bug #5871][Open] regexp \W matches some word characters when inside a case-insensitive character class — Gareth Adams <gareth@...>

14 messages 2012/01/09

[#42016] [ruby-trunk - Feature #5873][Open] Adopt FFI over DL — Heesob Park <phasis@...>

15 messages 2012/01/10

[#42149] [ruby-trunk - Feature #5899][Open] chaining comparsions. — Ondrej Bilka <neleai@...>

12 messages 2012/01/16

[#42164] [ruby-trunk - Feature #5903][Open] Optimize st_table (take 2) — Yura Sokolov <funny.falcon@...>

18 messages 2012/01/17

[ruby-core:41936] Re: feature request: marshallable proc's

From: Urabe Shyouhei <shyouhei@...>
Date: 2012-01-06 01:47:07 UTC
List: ruby-core #41936
On 2012年01月06日 08:54, Roger Pack wrote:
> Every so often I wish I could do something like
> a = background_process
> a.send {
>  # compute something long
> }
> 
> Which would require the ability to "serialize" proc's.
> So consider this my feature request.

Short answer: we wish we could.  And theoretically speaking it is not
impossible.  But no one have ever been successful.

> First thing that comes to mind would be the ability to translate them
> into an AST.
>  RubyVM::InstructionSequence.disassemble might be related.
> Cheers!

A proc is not a code snippet.  It is a "closure".  To serialize a closure
is not a easy job.  If you just want to inject a code snippet to another
process, you'd better propose something other than a proc serialization.

In This Thread