Continuation.yield limitations

[John Rose]

On Sep 10, 2019, at 1:46 AM, Andrew Haley <aph at redhat.com> wrote:
> 
> It's that when someone says "we don't know how to do X", my instinct
> is to say "Well, you may not." :-) Yeah, I know, I should sometimes
> suppress that instinct.

:-)

Like you, when I hear “it’s impossible to…” or even “nobody would even need to…”
I feel a certain stubbornness (or maybe courage) that jumps toward a contradiction.

Jane Austen’s Lizzie Bennet says it well:

> There is a stubbornness about me that never can bear to be frightened at the will of others. My courage always rises at every attempt to intimidate me.

> https://www.goodreads.com/quotes/120154-there-is-a-stubbornness-about-me-that-never-can-bear


That said, I do think wrangling the C compilers as you suggest would be a
lengthy process, with plenty of bugs along the way.  We did the equivalent to
HotSpot’s JIT, to allow frames to migrate between interpreted and compiled
modes, and it took a while to iron out all the kinks.  That work, in fact, is
probably one of the bases of the present work to allow JVM-controlled
frames to perform even more state changes.  Opening the game up to
non-JVM compilers is an exciting prospect, but won’t be allowed to detain
our releases.

— John