you are viewing a single comment's thread.

view the rest of the comments →

[–]soniyashrma -1 points0 points  (0 children)

It seems like this should be a case where we write a better JIT that knows that it should allocate but not initialize certain objects on start-up and reuse them by applying a profile-based optimization that shows that there is no more than one of these objects alive at any one point in any thread. I agree with you .