Currently the kV8CacheOptions flag allows picking among "disabled", "code", and "parser". "code" is the default, and my understanding is that that's not expected to change anytime soon (moreover, "parser" has bitrotted). I plan to remove the flag and the ability to to "parser" caching. Removing Chromium's dependency on that path will also allow us to remove it from V8's API (after a deprecation period).
Comment 1 by adamk@chromium.org
, Oct 30 2017