# The "Dependency cycles" Series

One of the most common complaints about F# is that it requires code to be in *dependency order*. That is, you cannot use forward references to code that hasn't been seen by the compiler yet.

In this series, I discuss dependency cycles, why they are bad, and how to get rid of them.

* [Cyclic dependencies are evil](/fsharpforfunandprofit/understanding-f/dependency-cycles/cyclic-dependencies.md). Cyclic dependencies: Part 1.
* [Refactoring to remove cyclic dependencies](/fsharpforfunandprofit/understanding-f/dependency-cycles/removing-cyclic-dependencies.md). Cyclic dependencies: Part 2.
* [Cycles and modularity in the wild](/fsharpforfunandprofit/understanding-f/dependency-cycles/cycles-and-modularity-in-the-wild.md). Comparing some real-world metrics of C# and F# projects.


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://swlaschin.gitbook.io/fsharpforfunandprofit/understanding-f/dependency-cycles.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.