Yesterday, Asumu Takikawa wrote:
> On 2012-06-21 13:03:18 -0400, Eli Barzilay wrote:
> > Nice. How about adding a big "deprecated" to the class100 docs,
> > and make a note to remove it in a year?
>
> That trick is neat, but would it be a problem to just remove it now?
Did you add some reminder
Agreed. Deprecate now, remove next+ or next++ release -- Matthias
On Jun 21, 2012, at 2:56 PM, Robby Findler wrote:
> I think we should give people warnings; we cannot just remove stuff.
>
> Robby
>
> On Thu, Jun 21, 2012 at 12:58 PM, Asumu Takikawa wrote:
>> On 2012-06-21 13:03:18 -0400,
I think we should give people warnings; we cannot just remove stuff.
Robby
On Thu, Jun 21, 2012 at 12:58 PM, Asumu Takikawa wrote:
> On 2012-06-21 13:03:18 -0400, Eli Barzilay wrote:
>> Nice. How about adding a big "deprecated" to the class100 docs, and
>> make a note to remove it in a year?
>
On Thu, Jun 21, 2012 at 1:58 PM, Asumu Takikawa wrote:
> On 2012-06-21 13:03:18 -0400, Eli Barzilay wrote:
>> Nice. How about adding a big "deprecated" to the class100 docs, and
>> make a note to remove it in a year?
>
> That trick is neat, but would it be a problem to just remove it now?
>
> Ton
On 2012-06-21 13:03:18 -0400, Eli Barzilay wrote:
> Nice. How about adding a big "deprecated" to the class100 docs, and
> make a note to remove it in a year?
That trick is neat, but would it be a problem to just remove it now?
Tony had the idea that we could just put it on PLaneT and tell people
About a month ago, as...@racket-lang.org wrote:
>
> cfe1711 Asumu Takikawa 2012-05-26 11:10
> :
> | Convert all uses of mzlib/class100 to racket/class
> :
Nice. How about adding a big "deprecated" to the class100 docs, and
make a note to remove it in a year?
(Eg, add this to the code:
(begi
6 matches
Mail list logo
