future

Language

clojure

Surface

keywords

Locale

pl

Concept

future

Brain ID

clojure/keywords/future

This locale has no distinct localized form; the canonical English token is shown.

Upstream reference

devdocs.io · search

Brain version

1.1.0-alpha.13 · generated Mon, 20 Jul 2026 15:26:24 GMT · hash 4914b8003cdd29d0…

Provenance

#18 concurrency-async concept_map maps clojure/future → concept future
#28 sealion-refinement concept_map maps clojure/future → concept future winning layer

Full per-leaf change history across brain builds is not yet recorded; shown is the current build's layer stack.

Discuss this term on the NADA forum →

Across locales

What each covering migration carries for this concept, per locale — the whole-brain view, not filtered by your language. Forms are the migration's leaf values (pre-transform, pre-human-verdict); a locale without a form falls back to canonical English. Chips open that locale's live docs page for this term.

concurrency-async · concept future — per-locale forms

Expand to load the per-locale matrix.

sealion-refinement · concept future — per-locale forms

Expand to load the per-locale matrix.

AI council review

Reviewed by 1 model · @cf/aisingapore/gemma-sea-lion-v4-27b-it · 2026-07-17

Cluster concurrency-async · locale pl · member future

improve

verdict

przyszłość

existing translation

future

improved translation

Explanation

Polish developers overwhelmingly use the loanword 'future' for async result objects. This avoids the misleading native translation.

Issue breakdown

consistency The native translation 'przyszłość' is misleading. Polish developers use 'future'.