> On Mar 14, 2016, at 12:28 PM, Steve Fink <[email protected]> wrote: > > Well, "the most aggressive compilation" is undecidable in general, since you > can't predict the future to know if some future execution won't invalidate > this or that constraint. But sure, I think we're basically agreeing, except > that I insist it'll only work if you phrase things as hints about things you > know about your code (such as that startup is now done and the honeymoon > period for latency is over), *not* as directives to do this or that. Engines > have to be free to ignore anything you say, and to choose the right thing to > do in response to a hint (which may be very different from what you'd guess > from the outside), and even then we can shoot ourselves in the foot if anyone > starts depending on things.
Let me apologize that I am not exactly the clearest on explaining myself sometimes. Anything I suggest I never expect to always work as engines involve, or mean the same thing, day to day, so hints is a much better term, that I’m perfectly fine with. I do know that, obviously, I’m attempting to push a language never meant to be one way towards another language, C. There’s some naivety in this. [>] Brian _______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
