Question 1

How do I migrate from core.typed to typedclojure?

Accepted Answer

Follow the upgrading instructions in the typedclojure repository's UPGRADING.md file. It involves updating dependencies from core.typed to typedclojure and may require adjustments to type annotations due to changes in the new version.

Question 2

Should I use core.typed or typedclojure for my new project?

Accepted Answer

For new projects, use typedclojure as it is actively maintained and supports newer Clojure versions. Core.typed is deprecated and only suitable for existing codebases on Clojure 1.10 or older that haven't migrated yet.

Question 3

How to add type annotations to a Clojure function with core.typed?

Accepted Answer

Use the `ann` macro from the core.typed library to specify types for functions and variables. Start by annotating critical parts of your code in a dev environment with the checker.jvm module enabled, then expand gradually.

Question 4

Does core.typed work with ClojureScript?

Accepted Answer

No, core.typed does not fully support ClojureScript; the JS modules are unreleased. For type checking in ClojureScript, consider alternatives or check if typedclojure offers better support, as core.typed is focused on JVM Clojure.

Question 5

What are the performance costs of using core.typed?

Accepted Answer

Core.typed adds compile-time overhead for type checking during development, which can slow down builds. However, the runtime.jvm module is designed to have minimal impact in production by separating type checking dependencies.

Question 6

How to handle dynamic code that core.typed can't type check?

Accepted Answer

You can use escape hatches like `any` types or disable type checking for specific namespaces. Core.typed allows mixing typed and untyped code, so you can gradually annotate while preserving dynamic parts.

core.typed

What is core.typed?

Overview

Use Cases

Best For

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions