Why still Clojure 1.4? · Issue #303 · 4clojure/4clojure · GitHub
Skip to content
This repository was archived by the owner on Dec 30, 2025. It is now read-only.
This repository was archived by the owner on Dec 30, 2025. It is now read-only.

Why still Clojure 1.4? #303

Closed as not planned
Closed as not planned
Why still Clojure 1.4?#303

Description

@laconiccrafts
laconiccrafts
opened on Jun 28, 2018

Is there a reason we are not using the latest version?

On a number of solutions I'm forced to rewrite my code in ways I'm not used to because the function I'd usually choose does not exist.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions