On Mon, Sep 2, 2013 at 11:16 AM, David Jeske <[email protected]> wrote:
> Therefore WRT BitC, we should be asking questions like: > > (a) is it a problem that string is implementing using runtime tricks which > are not avaiable to other apps? > If we are to be a systems language, then the answer is clearly "yes". The runtime implementations are safe for a reason. We should seek to make that reason expressible in the language, except where doing so would break other aspects of the language. > how can we make these capabilities available? > Most of what we are talking about is a combination of dependent type issues and enforcing readonly. > (b) is it a problem that users can't author their own > string-type-compatible string-slice type? If so, how should it be fixed? > It's an inevitability, because making everything virtual and relying on JIT to inline things isn't viable in a systems language. We can certainly assume that *some* implementations will use a JIT. Effective use of the language cannot rely on the availability of JIT. Jonathan
_______________________________________________ bitc-dev mailing list [email protected] http://www.coyotos.org/mailman/listinfo/bitc-dev
