Jump to content

Talk:Heap pollution

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia
This is an old revision of this page, as edited by AioftheStorm (talk | contribs) at 18:53, 16 July 2014 (This is less incomprehensible, but still needs work). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.
WikiProject iconJava Stub‑class Low‑importance
WikiProject iconThis article is within the scope of WikiProject Java, a collaborative effort to improve the coverage of Java on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.
StubThis article has been rated as Stub-class on Wikipedia's content assessment scale.
LowThis article has been rated as Low-importance on the project's importance scale.
WikiProject iconComputing: Software Stub‑class Low‑importance
WikiProject iconThis article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.
StubThis article has been rated as Stub-class on Wikipedia's content assessment scale.
LowThis article has been rated as Low-importance on the project's importance scale.
Taskforce icon
This article is supported by WikiProject Software (assessed as Mid-importance).

This is completely incomprehensible

The article does not define the term "heap pollution". It does not assert notability. It does not explain whether the problem is actually specific to Java or whether it has wider applicability--Dfeuer (talk) 05:21, 15 July 2014 (UTC)[reply]

This is less incomprehensible, but still needs work

An explanation of why the term "heap pollution" is used for the situation it describes would be very helpful. --Dfeuer (talk) 05:05, 16 July 2014 (UTC)[reply]

I'm afraid an explanation might be seen as original research, since Oracle who probably introduced the term didn't explicitly give a reason for calling it that, but I believe it is called heap pollution because you have a heap of parametrized objects that due to several possible reasons has become polluted with objects of a non-parametrized type, and this causes problems because when you have a parametrized variable referring to objects in that heap it will come across these nonparametrized objects and not know what to do with them. I am afraid though that I am unfamiliar with Java and haven't dabbled in it for ages because, frankly, C++ is a better language, but the term was first introduced when discussing Java and I believe there are problems specific to it in Java. I agree the article is confusing, but someone more familiar with Java than I will have to clear it up.AioftheStorm (talk) 18:53, 16 July 2014 (UTC)[reply]