> For the complete documentation index, see [llms.txt](https://ola-foundation.gitbook.io/ola-lang/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ola-foundation.gitbook.io/ola-lang/ola-language/features-todo.md).

# Features TODO

## Constructor

Currently, Ola smart contracts do not support constructors. Initialization can only be done manually within the contract by writing methods like init. Constructors and state variable initialization will be supported in the future.

## Transaction revert

Currently, when an error occurs during transaction execution in Ola smart contracts, specific revert information is not provided. This will be supported in the future.

## Inheritance and polymorphism

Currently, Ola smart contracts support interfaces and libraries but lack contract inheritance. This will be supported in the future.

## Contract constants

Currently, Ola does not support constants because it requires a dedicated constant storage area to be set up on the backend. This will be supported in the future.


---

# 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 dynamically by asking a question.

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

```
GET https://ola-foundation.gitbook.io/ola-lang/ola-language/features-todo.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.