From: "Юрий Соколов" <funny.falcon@...>
Date: 2016-04-28T10:06:21+03:00
Subject: [ruby-core:75236] Re: [Ruby trunk Feature#10548] remove callcc (Callcc is now going obsoleted. Please use Fiber.)

--===============1771419333==
Content-Type: multipart/alternative; boundary=001a1136369edbd68305318629e5

--001a1136369edbd68305318629e5
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

You can easily reimplement your solver passing block to `choose`.
Certainle, it will be less readable, but will work.
27 =D0=B0=D0=BF=D1=80. 2016 =D0=B3. 2:36 PM =D0=BF=D0=BE=D0=BB=D1=8C=D0=B7=
=D0=BE=D0=B2=D0=B0=D1=82=D0=B5=D0=BB=D1=8C <l.rieder@gmail.com> =D0=BD=D0=
=B0=D0=BF=D0=B8=D1=81=D0=B0=D0=BB:

> Issue #10548 has been updated by Lukas Rieder.
>
>
> **Please keep callcc, they are inherently awesome to build constraint
> solvers.**
>
> I am using them in a real life application. I am calculating the availabl=
e
> tables for a full calendar with many time slots and with respect to many
> configurable business rules for restaurants.
> Using callcc this feature got blazingly fast and very nicely readable.
> Also we use it to optimise table arrangements with respect to complex
> restaurant business rules (even something like: Guest A doesn't like to s=
it
> near Guest B).
>
> Please just have a look at these resources:
>
> * https://github.com/chikamichi/amb/tree/master/examples
> *
> http://web.archive.org/web/20151116124853/http://liufengyun.chaos-lab.com=
/prog/2013/10/23/continuation-in-ruby.html
>
> ----------------------------------------
> Feature #10548: remove callcc (Callcc is now going obsoleted.  Please use
> Fiber.)
> https://bugs.ruby-lang.org/issues/10548#change-58356
>
> * Author: Masaya Tarui
> * Status: Open
> * Priority: Normal
> * Assignee:
> ----------------------------------------
>
> 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/DevelopersMeeting20140517Ja=
pan
> ,
> matz agreed to remove callcc.
>
> If there is no refutation, remove callcc in the future version.
>
>
>
> --
> https://bugs.ruby-lang.org/
>
> Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=3Dunsubscrib=
e>
> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>
>

--001a1136369edbd68305318629e5
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<p dir=3D"ltr">You can easily reimplement your solver passing block to `cho=
ose`.<br>
Certainle, it will be less readable, but will work.<br>
</p>
<div class=3D"gmail_quote">27 =D0=B0=D0=BF=D1=80. 2016 =D0=B3. 2:36 PM =D0=
=BF=D0=BE=D0=BB=D1=8C=D0=B7=D0=BE=D0=B2=D0=B0=D1=82=D0=B5=D0=BB=D1=8C  &lt;=
<a href=3D"mailto:l.rieder@gmail.com">l.rieder@gmail.com</a>&gt; =D0=BD=D0=
=B0=D0=BF=D0=B8=D1=81=D0=B0=D0=BB:<br type=3D"attribution"><blockquote clas=
s=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;pad=
ding-left:1ex">Issue #10548 has been updated by Lukas Rieder.<br>
<br>
<br>
**Please keep callcc, they are inherently awesome to build constraint solve=
rs.**<br>
<br>
I am using them in a real life application. I am calculating the available =
tables for a full calendar with many time slots and with respect to many co=
nfigurable business rules for restaurants.<br>
Using callcc this feature got blazingly fast and very nicely readable. Also=
 we use it to optimise table arrangements with respect to complex restauran=
t business rules (even something like: Guest A doesn&#39;t like to sit near=
 Guest B).<br>
<br>
Please just have a look at these resources:<br>
<br>
* <a href=3D"https://github.com/chikamichi/amb/tree/master/examples" rel=3D=
"noreferrer" target=3D"_blank">https://github.com/chikamichi/amb/tree/maste=
r/examples</a><br>
* <a href=3D"http://web.archive.org/web/20151116124853/http://liufengyun.ch=
aos-lab.com/prog/2013/10/23/continuation-in-ruby.html" rel=3D"noreferrer" t=
arget=3D"_blank">http://web.archive.org/web/20151116124853/http://liufengyu=
n.chaos-lab.com/prog/2013/10/23/continuation-in-ruby.html</a><br>
<br>
----------------------------------------<br>
Feature #10548: remove callcc (Callcc is now going obsoleted.=C2=A0 Please =
use Fiber.)<br>
<a href=3D"https://bugs.ruby-lang.org/issues/10548#change-58356" rel=3D"nor=
eferrer" target=3D"_blank">https://bugs.ruby-lang.org/issues/10548#change-5=
8356</a><br>
<br>
* Author: Masaya Tarui<br>
* Status: Open<br>
* Priority: Normal<br>
* Assignee:<br>
----------------------------------------<br>
<br>
We are paying a lot of costs for callcc&#39;s consistency.<br>
and currently, we can use Fiber in many situation.<br>
<br>
In <a href=3D"https://bugs.ruby-lang.org/projects/ruby/wiki/DevelopersMeeti=
ng20140517Japan" rel=3D"noreferrer" target=3D"_blank">https://bugs.ruby-lan=
g.org/projects/ruby/wiki/DevelopersMeeting20140517Japan</a>,<br>
matz agreed to remove callcc.<br>
<br>
If there is no refutation, remove callcc in the future version.<br>
<br>
<br>
<br>
--<br>
<a href=3D"https://bugs.ruby-lang.org/" rel=3D"noreferrer" target=3D"_blank=
">https://bugs.ruby-lang.org/</a><br>
<br>
Unsubscribe: &lt;mailto:<a href=3D"mailto:ruby-core-request@ruby-lang.org">=
ruby-core-request@ruby-lang.org</a>?subject=3Dunsubscribe&gt;<br>
&lt;<a href=3D"http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core=
" rel=3D"noreferrer" target=3D"_blank">http://lists.ruby-lang.org/cgi-bin/m=
ailman/options/ruby-core</a>&gt;<br>
</blockquote></div>

--001a1136369edbd68305318629e5--

--===============1771419333==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline


Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>

--===============1771419333==--