diff options
Diffstat (limited to 'docs/commentary/stability.html')
| -rw-r--r-- | docs/commentary/stability.html | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/commentary/stability.html b/docs/commentary/stability.html index 9e12ef34..6c23680f 100644 --- a/docs/commentary/stability.html +++ b/docs/commentary/stability.html @@ -5,7 +5,7 @@ </head> <div class="nav">(<a href="https://github.com/mlochbaum/BQN">github</a>) / <a href="../index.html">BQN</a> / <a href="index.html">commentary</a></div> <h1 id="is-bqn-stable"><a class="header" href="#is-bqn-stable">Is BQN stable?</a></h1> -<p>The short answer is that code running online or in CBQN is unlikely to break. In rare cases we add experimental system values (the <code><span class='Value'>•</span></code> things) before we're ready to commit to a particular design; read further or check on the forums if you'd like to know the status of a particular system function.</p> +<p>The short answer is that code running online or in CBQN is unlikely to break. In rare cases we add experimental system values (the <code><span class='Value'>•</span></code> things) before we're ready to commit to a particular design; read further or check on the forums if you'd like to know the status of a particular system function. And we are still making some backwards-compatible additions of moderate importance to core BQN: see <a href="https://topanswers.xyz/apl?q=1888">this page</a>. So it's possible that that extra knowledge will be needed to keep up with BQN in the future, but only a small amount.</p> <p>I have thousands of lines of running BQN code including the self-hosted sources, website generator, and Singeli compiler. There are also now many BQN examples and REPL links <a href="../community/index.html">spread</a> across the web which would be harder to change. So there is a strong reason to maintain compatibility for common or even moderately used features. Because BQN's been designed in a conservative way, avoiding fiddly decisions by keeping things simple, it seems that few compatibility breaks will be required. The history so far seems to bear this out.</p> <p>Various edge cases were fixed when I first ran the primitive specifications through unit tests(!) in February 2021. Since then there has been a single compatibility break, that is, change from one intentional (i.e. excluding bugs) non-error behavior to a different behavior.</p> <ul> |