Dag Sverre Seljebotn wrote: > Dag Sverre Seljebotn wrote: > >> What do I propose instead? >> a) That the reference-counted heap-allocated array stuff in the wiki >> is implemented first (with a list constructor). So the thing gets the >> semantics of a reference counted array, constructed again each time it >> is assigned (very similar to a Python list). >> >> b) That simple cases (where the pointer is never reassigned or copied, >> only written/read to/from by indexing) are then optimized to use stack >> allocation instead. >> > > First and foremost the point now is to .
Sorry! I meant: The point now was to argue for postponing the decision for later and disable it in the upcoming release. I'd settle for disabling any "literal assignment" to the pointer outside of the declaration though, then I'd be back to "not worrying". (One could also disable it only inside loops, but that is too ugly and inconsistent.) -- Dag Sverre _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
