# Version 1.0 released of Nim Programming Language

**URL:** <https://discourse.julialang.org/t/version-1-0-released-of-nim-programming-language/29099>\
**Category:** Offtopic\
**Created:** [September 24, 2019, 2:48am UTC](https://discourse.julialang.org/t/version-1-0-released-of-nim-programming-language/29099 "2019-09-24T02:48:42Z")\
**Posts on this page:** 1\
**Showing post:** 52

<div class="post-metadata">

**Author:** ![StefanKarpinski](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/stefankarpinski/32/24_2.png) [@StefanKarpinski](https://discourse.julialang.org/u/StefanKarpinski)\
**Post date:** [September 26, 2019, 4:24pm UTC](https://discourse.julialang.org/t/version-1-0-released-of-nim-programming-language/29099/52 "2019-09-26T16:24:36Z")

</div>

> [@mratsim](#):
>
> If I understood correctly, you want to know if incompatible API changes, will be caught at compile-time, yes.

No, that’s not what I’m asking. Static languages traditionally have well-defined rules about what qualifies as a well-typed program and what doesn’t. These rules are part of the definition of the language and guarantee that the compiler can determine what the types of all values are. I cannot find any such rules explained anywhere for Nim. I’d like to know what they are.

---

_[View the full topic](https://discourse.julialang.org/t/version-1-0-released-of-nim-programming-language/29099)._
