<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<meta name="generator" content="Asciidoctor 2.0.23">
<title>WishList</title>
<link rel="stylesheet" href="https://fonts.googleapis.com/css?family=Open+Sans:300,300italic,400,400italic,600,600italic%7CNoto+Serif:400,400italic,700,700italic%7CDroid+Sans+Mono:400,700">
<link rel="stylesheet" href="./asciidoctor.css">
<link rel="stylesheet" href="./mlton.css">

</head>
<body class="article">
<div id="mlton-header">
<div id="mlton-header-text">
<h2>
<a href="./Home">
MLton
20241230
</a>
</h2>
</div>
</div>
<div id="header">
<h1>WishList</h1>
</div>
<div id="content">
<div id="preamble">
<div class="sectionbody">
<div class="paragraph">
<p>This page is mainly for recording recurring feature requests.  If you
have a new feature request, you probably want to query interest on one
of the <a href="Contact">mailing lists</a> first.</p>
</div>
<div class="paragraph">
<p>Please be aware of MLton&#8217;s policy on
<a href="LanguageChanges">language changes</a>.  Nonetheless, we hope to provide
support for some of the "immediate" <a href="SuccessorML">SuccessorML</a> proposals in a
future release.</p>
</div>
</div>
</div>
<div class="sect1">
<h2 id="_support_for_link_options_in_ml_basis_files">Support for link options in ML Basis files</h2>
<div class="sectionbody">
<div class="paragraph">
<p>Introduce a mechanism to specify link options in <a href="MLBasis">ML Basis</a>
files.  For example, generalizing a bit, a ML Basis declaration of the
form</p>
</div>
<div class="listingblock">
<div class="content">
<pre>option "option"</pre>
</div>
</div>
<div class="paragraph">
<p>could be introduced whose semantics would be the same (as closely as
possible) as if the option string were specified on the compiler
command line.</p>
</div>
<div class="paragraph">
<p>The main motivation for this is that a MLton library that would
introduce bindings (through <a href="ForeignFunctionInterface">FFI</a>) to an
external library could be packaged conveniently as a single MLB file.
For example, to link with library <code>foo</code> the MLB file would simply
contain:</p>
</div>
<div class="listingblock">
<div class="content">
<pre>option "-link-opt -lfoo"</pre>
</div>
</div>
<div class="paragraph">
<p>Similar feature requests have been discussed previously on the mailing lists:</p>
</div>
<div class="ulist">
<ul>
<li>
<p><a href="http://www.mlton.org/pipermail/mlton/2004-July/025553.html" class="bare">http://www.mlton.org/pipermail/mlton/2004-July/025553.html</a></p>
</li>
<li>
<p><a href="http://www.mlton.org/pipermail/mlton/2005-January/026648.html" class="bare">http://www.mlton.org/pipermail/mlton/2005-January/026648.html</a></p>
</li>
</ul>
</div>
</div>
</div>
</div>
<div id="mlton-footer">
<div id="mlton-footer-text">
<div>
Last updated Thu Oct 21 15:53:06 2021 -0400 by Matthew Fluet.
<a href="https://github.com/MLton/mlton/commits/master/doc/guide/src/WishList.adoc">Log</a>
<a href="https://github.com/MLton/mlton/edit/master/doc/guide/src/WishList.adoc">Edit</a>
</div>
</div>
</body>
</html>