-
Notifications
You must be signed in to change notification settings - Fork 5k
Delete FEATURE_INTERPRETER #111137
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Delete FEATURE_INTERPRETER #111137
Conversation
FEATURE_INTERPRETER is a poorly architected implementation of an interpreter. Proper interpreter implementation should start with a clean slate.
Tagging subscribers to this area: @mangod9 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thank you!
Is this because a new interpreter implementation is imminent? |
There's also: https://github.com/dotnet/runtime/blob/main/eng/pipelines/coreclr/clrinterpreter.yml to delete. I couldn't find the actual pipeline in AzDO; it hasn't run for a while so maybe it got garbage collected. Also, |
Yes. |
Could be interesting for mobile development. I heard of an experiment done at a former employer where the startup time of the (enormous) Java/Android app was actually faster in interpreted mode due to reduced I/O (... on some phones, mind you). |
FEATURE_INTERPRETER is a poorly architected implementation of an interpreter. Proper interpreter implementation should start with a clean slate.