> For the complete documentation index, see [llms.txt](https://docs.flatredball.com/flatredball/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flatredball.com/flatredball/tutorials/code-tutorials/tutorials-dictionaries-and-enum-keys.md).

# Dictionaries and Enum Keys

### Introduction

Enums are a very common type of object used in dictionaries. Unfortunately there is a hidden behavior in dictionaries that use enums as their keys which can cause performance problems - usually resulting from memory allocation.

### Our example

Consider the following simple example:

```
public enum Day
{
   Monday,
   Tuesday,
   Wednesday
}

// later we define a Dictionary:
Dictionary<Day, int> mSomeDictionary = new Dictionary<Day, int>();

// and finally you may want to check the dictionary for whether it contains a key:
Day day = Day.Monday;
if(mSomeDictionary.ContainsKey(day))
{
   // do something
}
```

While that may seem like code that shouldn't case problems, unfortunately under the hood .NET casts the enum to an object to perform the equality check. This cast takes far more time than an integer comparison, and it also creates garbage, which can be fatal on the Xbox 360. If you'd like to read more, check [this blog post](http://beardseye.blogspot.com/2007/08/nuts-enum-conundrum.html).

### How to fix it

The easiest way to fix this problem is to simply use ints and cast your enums as follows:

```
public enum Day
{
   Monday,
   Tuesday,
   Wednesday
}

// later we define a Dictionary:
Dictionary<int, int> mSomeDictionary = new Dictionary<int, int>();

// and finally you may want to check the dictionary for whether it contains a key:
Day day = Day.Monday;
if(mSomeDictionary.ContainsKey((int)day))
{
   // do something
}
```

This will completely eliminate any allocation that will occur in your ContainsKey call.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.flatredball.com/flatredball/tutorials/code-tutorials/tutorials-dictionaries-and-enum-keys.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.