maiko: Fate of NATIVETRAN #89
-
There's some code involved here, like There's also this from
There's also all of It looks like this has some complications spread through the code, never worked, never shipped, and even in the old comments, is noted as obsolete. |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 1 reply
-
Native Translation (transforming sequence of byte codes to native code) isn't on the path to any of our various goals. The only reason to do it would be performance, which isn't the point and there are lots of ways it wouldn't work out. |
Beta Was this translation helpful? Give feedback.
-
FYI: @nbriggs But this isn't as easy as just removing things that are |
Beta Was this translation helpful? Give feedback.
-
It's also the case that removing it isn't really on the path to finding the other problems, so while removing the hooks may be a worthy goal in the longer term I don't think it's near the top of any priority list. |
Beta Was this translation helpful? Give feedback.
-
i converted this from an Issue to a Discussion in the "implementation history" category, following the principle that Issues should be reserved for things that are acdtionable, that someone could self-assign and make progress on, and other things are Discussions of general topics or trying to come up with policy. At lease that is how I read the intention of the feature. |
Beta Was this translation helpful? Give feedback.
Native Translation (transforming sequence of byte codes to native code) isn't on the path to any of our various goals. The only reason to do it would be performance, which isn't the point and there are lots of ways it wouldn't work out.
Transforming to little-endian and 64-bit pointers would be a lot easier. Nuke it.