[Swift-devel] new coaster code

[Mihael Hategan]

On Mon, 2009-05-18 at 11:47 -0500, Zhao Zhang wrote:
> Hi, Mihael
> 
> Does this mean that the "Block Allocation" and "Dynamic Allocation" 
> could not coexist? By Dynamic Allocation, I mean
> the one is currently working in coaster.

Don't use the term "Dynamic allocation".

You can make the block allocation code behave in a manner similar to the
old code by tweaking the settings. My point is not about intended
behavior, but about actual code. The old code won't be there along with
the new code.

> 
> zhao
> 
> Mihael Hategan wrote:
> > In the development of the block allocation code, I had to make a
> > decision not to keep backwards compatibility (i.e. have both the old
> > code and the block allocation code simultaneously useable). This is due
> > to:
> >
> > 1. The old code, while working, had problems that in the long run didn't
> > seem like a good idea to have.
> > 2. It's easier, from a development perspective, to not have to abstract
> > over two fairly different implementations of a sub-system.
> >
> > What this means is that once I commit the block allocation code, the old
> > behavior is gone, and if you learned to rely on its peculiarities, that
> > won't work.
> >
> > So I'm trying to ask folks how they would like to see this handled.
> > Opinions, suggestions, etc.
> >
> > Mihael
> >
> > _______________________________________________
> > Swift-devel mailing list
> > Swift-devel at ci.uchicago.edu
> > http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
> >
> >