'Futuristic' Unison functional language debuts

"Unison, a statically typed functional language with type inference, an effect system, and advanced tooling, has reached its 1.0 release status. Announced November 25, Unison 1.0 marks a point where the language, distributed runtime, and developer workflow have stabilized, according to Unison Computing. Billed as "a friendly programming language from the future," Unison is purported to bring benefits in compilation and distributed system development."

"With Unison, a definition is identified by its actual contents, i.e. a hash of its syntax tree, not just by the human-friendly name that also referred to older versions of the definition, according to Unison. As a result, each Unison definition has a unique and deterministic address. All named arguments are replaced by positionally-numbered variable references, and all dependencies are replaced by their hashes. Thus, the hash of each definition uniquely identifies its exact implementation and pins down all its dependencies, according to Unison."

"The Unison ecosystem leverages this core idea from the ground up. Benefits include never compiling the same code twice and limiting versioning conflicts. Further, Unison simplifies distributed programming. Because definitions in Unison are identified by a content hash, arbitrary computations can be moved from one location to another, with missing dependencies deployed on the fly. Unison can be viewed as a descendant of Haskell, with similarities including type inference and pattern matching, but is smaller and simpler than Haskell, according to a Unison FAQ."

Unison 1.0 marks a stabilization of the language, distributed runtime, and developer workflow. The language is statically typed with type inference, an effect system, and advanced tooling. Each definition is content-addressed: identified by a hash of its syntax tree rather than by mutable human-friendly names. Named arguments become positionally-numbered references and dependencies are replaced by their hashes, giving each definition a unique, deterministic address that pins implementations and dependencies. The ecosystem leverages content addressing to avoid recompiling identical code, reduce version conflicts, and enable moving computations across machines with missing dependencies deployed on demand. Unison resembles Haskell in type inference and pattern matching while aiming for smaller simplicity.

Read at InfoWorld