> For the complete documentation index, see [llms.txt](https://cs61b-2.gitbook.io/cs61b-textbook-spring-2026/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cs61b-2.gitbook.io/cs61b-textbook-spring-2026/9.-inheritance-ii-extends-casting-higher-order-functions/9.1-subtype-polymorphism-vs.-function-passing.md).

# 9.1 Polymorphism vs. Function Passing

**Operator Overloading**

Suppose we define a Dog class:

```python
class Dog:
   def __init__(self, name, size):
       self.name = name
       self.size = size
  
   def __gt__(self, other):
       return self.size > other.size
```

The Python code below can be used to find the maximum Dog in a list of Dogs.

```python
def get_the_max(x):
   max_value = x[0]
   for item in x:
       if item > max_value:
           max_value = item
   return max_value

max_dog = get_the_max(doglist)
```

The get\_the\_max function in Python is general and can work on any type. It achieves this generality by harnessing "operator overloading".

More generally, this ability to handle any type is sometimes called "polymorphism", which I'll define via wikipedia as “the ability in programming to present the same programming interface for differing underlying forms” \[[wiki](https://en.wikipedia.org/wiki/Polymorphism)]

In this case, the > operator allows to compare anything (i.e. "any underlying form") in Python. In turn the definition of > is given by `__gt__`.


---

# 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://cs61b-2.gitbook.io/cs61b-textbook-spring-2026/9.-inheritance-ii-extends-casting-higher-order-functions/9.1-subtype-polymorphism-vs.-function-passing.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.