Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
How are enums handled when it comes to the heap, memory, and when an enum type instance is created? If I’ve got an enum with fifty field constants, then do I have fifty objects on the heap representing that enum type (when accessed), and are there performance concerns?
The first time the type is accessed and it gets initialized, a new object is created for each value. However, unless you have a huge number of instance fields in the enum, each object will be very small. I’d be very surprised to see a situation in which this was a real performance concern unless you were on a massively constrained device.