> > It's much more complicated than that. What if a library returns an > > object or an array to another library? > The same that happens in C now, memory management is part of the interface > and you should state if the returned object's memory is managed by the > library or the user.
library or user Could we have some "typedef" for this, or is it not practical? > This introduces a problem D doesn't have now, but let's keep the focus > here, this will be used mostly only in embedded environments, where this > problem is already present, so it's not too bad. People using "regular" > D probably won't be using any "embedded library". They other way arround > could be a little more likely, and since "embedded guys" are tought, they > should be able to cope with this issue (or avoid using "regular" > D libraries that use the GC). > > Memory allocation strategy is a cross-cutting concern. > Yes.