reml(1)

πŸ“¦
version 4.7.23 Β· 2 versions
, in nixpkgs unstable

πŸ’– NAME πŸ’–

reml β€” Standard ML with Explicit Regions and Effects, bestie ✨ (and yes, this is the reml(1) page straight out of MLKit, a compiler for Standard ML 🫢)


🌸 SYNOPSIS 🌸

reml [OPTION]... [file.sml | file.sig | file.mlb]

Every single possible option is listed below. Like, all of them. We do not gatekeep here πŸ’…


πŸŽ€ DEFAULTS πŸŽ€

Okay so before you even touch a flag, here's exactly where everything sits out of the box. The whole lineup, no skipping πŸ‘‘:

  • --SML_LIB β†’ You_did_not_set_path_to_install_dir (iconic placeholder energy fr πŸ’€)
  • -aopt β†’ off
  • --alloc_protect_always β†’ off
  • -argo β†’ off
  • -as β†’ as --64
  • -verbose β†’ off
  • --comments_in_asmcode β†’ off
  • -c β†’ off
  • -timings β†’ off
  • -cfold β†’ on
  • --contract β†’ on
  • -cr β†’ off
  • -cross_opt β†’ on
  • -dangle β†’ on
  • --dangling_pointers_statistics β†’ off
  • -debug β†’ off
  • -dcs β†’ off
  • --debug_linking β†’ off
  • --debug_man_enrich β†’ off
  • -Dpar β†’ off
  • --debug_which_at β†’ off
  • --delete_target_files β†’ on
  • --disable_atbot_analysis β†’ off
  • --disable_flow_var β†’ off
  • -dufa β†’ on
  • --eliminate_explicit_records β†’ on
  • --fix_floating β†’ on
  • -g β†’ off
  • --high_pointer_tagging β†’ on
  • -basislib β†’ on
  • --inline_functors β†’ off
  • --libs β†’ m,c,dl
  • -ldexe β†’ gcc
  • -ldshared β†’ gcc
  • -ltdce β†’ on
  • --log_to_file β†’ off
  • -max_inl_sz β†’ 200
  • -max_spec_sz β†’ 200
  • --messages β†’ on
  • --minimize_fixs β†’ on
  • --namebase β†’ dummyBase
  • --objs β†’ off
  • -opt β†’ on
  • -o β†’ run
  • -j β†’ 1
  • -par β†’ on
  • -par0 β†’ off
  • -ptc β†’ on
  • --pretty_depth β†’ 5
  • --pretty_string_size β†’ 80
  • --print_K_normal_forms β†’ off
  • -Ppp β†’ off
  • -Paux β†’ on
  • --print_bit_vectors β†’ off
  • --print_calc_offset_program β†’ off
  • -Pcee β†’ off
  • -Pccp β†’ off
  • -Pceb β†’ off
  • --print_constraints β†’ off
  • -abbrev β†’ on
  • --print_control_prefix_infix β†’ off
  • -Pdre β†’ off
  • -Pdresm β†’ off
  • -Peffects β†’ off
  • --print_excon_name β†’ off
  • -Peb β†’ off
  • --print_fetch_and_flush_program β†’ off
  • --print_linearised_program β†’ off
  • --print_lvar_name β†’ off
  • --print_normalized_program β†’ off
  • -Pole β†’ off
  • -Ppse β†’ off
  • -Ppeast β†’ off
  • -Prfg β†’ off
  • -Prip β†’ off
  • -Prsp β†’ off
  • -Prse0 β†’ off
  • -Pregions β†’ on
  • --print_register_allocated_program β†’ off
  • --print_rho_levels β†’ off
  • -Prho_protection β†’ off
  • --print_rho_types β†’ off
  • --print_simplified_program β†’ off
  • -Psme β†’ off
  • -Ptypestamps β†’ off
  • -Ptypes β†’ off
  • --raggedRight β†’ on
  • -scratch β†’ off
  • -ri β†’ on
  • -prof β†’ off
  • --register_allocation β†’ on
  • --reml β†’ on
  • --report_boxities β†’ off
  • -sig β†’ off
  • --safeLinkTimeElimination β†’ off
  • --specialize_recursive_functions β†’ on
  • -stats_opt β†’ off
  • --strip β†’ off
  • --type_check_lambda β†’ on
  • --unbox_funargs β†’ on
  • --unbox_real_funargs β†’ on
  • --unbox_reals β†’ on
  • -uncurry β†’ on
  • --warn_on_escaping_puts β†’ off
  • --warn_on_parallel_puts β†’ off
  • -w β†’ 100

πŸ¦‹ DESCRIPTION πŸ¦‹

Okay so ReML is Standard ML with support for programming with explicit regions, explicit effects, and effect constraints. That's the whole vibe. With ReML, atomic effects include get-effects, put-effects, and mut-effects, and the parallel thread support is right there. What it does not do: ReML does not support integration with reference-tracing garbage collection. Noted, respected, moving on πŸ’…

When you invoke reml, it will compile the specified sources into an executable file, run through a whole series of translation phases β€” think of it as the compiler's main-character arc 🌈. The various options let you control the printing of intermediate forms and control which optimizations get performed. So if you're nosy (affectionate), there's a flag for that.

If your source files are organised in ML Basis Files (files with extension .mlb), the compiler will memoize symbol table information and object code in the dedicated MLB directories located relative to the source files. Caching! We love a queen who remembers things πŸŽ€

If reml is invoked without source files, an interactive REPL starts up instead. Type ':help;' within the REPL to learn more about how to use it β€” it's giving built-in bestie 🫢

To learn more about programming with ReML, consult the MLKit web page at

http://melsman.github.io/mlkit

⭐ STANDARDS ⭐

ReML is based on the MLKit. The MLKit implements Standard ML (Revised 1997) and has almost full support for the Standard ML Basis Library (version of 2002) β€” like, almost full, bestie, don't come for me 😭. See the MLKit home page for a detailed overview of the support for the Standard ML Basis Library.


πŸ”₯ EXAMPLES πŸ”₯

For examples, consult the files in the 'test/reml' folder within the github repository at http://github.com/melsman/mlkit. Real code, real receipts, go look πŸ‘‘


✨ OPTIONS ✨

Here's the full menu. Every flag, every default, no cap πŸ’–

  • --SML_LIB S β€” the installation directory for the MLKit standard library. For normal execution you should not modify this value, okay? But if you wish to use the MLKit with an altered runtime system, you can update this setting and the system will try to link to a runtime system found in the specified install directory. Fancy πŸ¦‹
  • --aggressive_opt, -aopt β€” enable aggressive optimisations, including aggressive inlining. Heads up though: these optimisations are not guaranteed to be region safe. Also, turning off garbage collection automatically turns off this option. It's giving "do it for the plot" πŸ’€
  • --alloc_protect_always β€” always protect allocation when parallelism is enabled. Like, disregard the result of protection inference entirely. Overprotective? Maybe. Safe? Yes πŸ›‘οΈ
  • --argobots, -argo β€” when enabled, executables link with the Argobots lightweight thread library. Threads but make it lightweight 🌸
  • --assembler S, -as S β€” specifies the assembler used. On Linux the default is 'as --64'. On macOS, the default is 'as -q'. Pick your fighter πŸ’…
  • --chat, -verbose β€” print a message for each compilation step in the compiler. It literally will not stop talking and honestly? Same 😭
  • --comments_in_asmcode β€” insert comments in assembler code. Little notes for future you πŸŽ€
  • --compile_only, -c β€” compile only. Suppresses generation of executable.
  • --compiler_timings, -timings β€” show compiler timings for each compilation phase. Time the tea β˜•
  • --constant_folding, -cfold β€” enable constant folding optimisations.
  • --contract β€” Contract is responsible for inlining, specialization, elimination of dead code, and much else. It's the Lambda Expression Optimiser, and yes, it's the main character πŸ‘‘
  • --contract_regions, -cr β€” when this option is enabled, identically typed regions bound by the same letregion construct are unified. Moreover, region parameters to non-exported functions are trimmed whenever possible. Tidy ✨
  • --cross_module_opt, -cross_opt β€” enable cross-module optimisation, including inlining of small functions and specialisation of small recursive functions. Which optimisations are performed across modules is controlled by individual optimisation flags. Teamwork makes the dream work 🫢
  • --dangling_pointers, -dangle β€” when this option is disabled, dangling pointers are avoided by forcing values captured in closures to live at least as long as the closure itself. And to make garbage collection sound, this option is disabled by default when garbage collection is enabled. Important safety moment ⚠️
  • --dangling_pointers_statistics β€” when enabled, the compiler prints statistics about the number of times strengthening of the region typing rules (to avoid dangling pointers during evaluation) effects the target program. This flag is useful only when the flag -gc or -no_dangle is enabled. Yes, that's exactly how it's worded. Numbers girlies rise πŸ™ˆ
  • --debug_compiler, -debug β€” print intermediate forms of a program during compilation. Peek behind the curtain 🎭
  • --debug_constraint_solving, -dcs β€” debug ReML constraint solving.
  • --debug_linking β€” debug linking of target code by showing which object files are linked together. It's giving receipts πŸ”
  • --debug_man_enrich β€” show information about why a program unit need be recompiled. A program unit (or a functor body) is recompiled if either (a) the program unit is modified, or (b) information about an identifier for which the program unit depends upon has changed. Detective mode πŸ•΅οΈ
  • --debug_parallelism, -Dpar β€” debug parallelism, including protection inference.
  • --debug_which_at β€” debug storage mode analysis.
  • --delete_target_files β€” delete assembler files produced by the compiler. If you disable this flag, you can inspect the assembler code produced by the compiler. Your choice: clean workspace or hot gossip πŸ“
  • --disable_atbot_analysis β€” disable storage mode analysis. That is, turn all allocation directives into attop.
  • --disable_flow_var β€” disable optimised compilation of control-flow code, such as conditional expressions.
  • --drop_unused_funargs, -dufa β€” drop function arguments that are unused. If nobody's using it, it's gone πŸ’…
  • --eliminate_explicit_records β€” eliminate bindings of explicit records only used for selections. Transform
let r = (e1,...,en) in ... #i r .. #j r ...

into

let x1=e1 in ... let xn=en in ... xi .. xj ...

(Lambda Expression Optimiser). Decluttered, slayed ✨

  • --fix_floating β€” float fix-bindings into immediate let-bindings when possible, to help tail-calls not be captured in let- region bindings.
  • --gdb_support, -g β€” when enabled, the compiler passes the option --gstabs to as (The GNU Assembler) and preserves the generated assembler files (.s files). Passing the --gstabs option to as makes it possible to step through the generated program using gdb (The GNU Debugger). Debug era πŸ’€
  • --help β€” print extended help information and exit.
  • --help S β€” print help information about an option and exit. Yes, the argument comes after. Ask about one thing at a time bestie πŸŽ€
  • --high_pointer_tagging β€” when enabled, the 16 most-significant bits in pointers may be used for tagging. Smuggling data in the top bits, iconic πŸ‘‘
  • --import_basislib, -basislib β€” import Basis Library automatically in your projects. If you wish to make use of the Standard ML Basis Library in your projects, this option should be turned on β€” unless you wish to import the Basis Library manually in your projects. Then do you πŸ’…
  • --inline_functors β€” inline functors during static interpretation instead of generating separate target code blocks for functor bodies and arguments. With the flag enabled, performance may increase, at the cost of larger (re)compilation times. The flag may be controlled in mlb-files using mlb-annotations. Trade-offs, always trade-offs 😭
  • --inline_names S β€” names of functions that should always be inlined if possible, no matter the setting of the flag --maximum_inline_size. These ones get the VIP pass 🎟️
  • --libdirs S β€” controls where ld looks for archives. The format is a comma-separated list of directories; see the -libs entry. The default is the empty list; thus 'ld' will look for libraries in only the system specific default directores. The directories are passed to 'ld' using the -L option. (Yes, "directores". We keep it exactly as written πŸ’–)
  • --libs S β€” for accessing a foreign function residing in an archive named libNAME.a from Standard ML code (using prim), you need to add 'NAME' to this comma-separated list. Notice that an object file (with extension '.o') is an archive if it is renamed to have extension '.a'. You may need to use the -libdirs option for specifying directories for which ld should look for library archives. The libraries are passed to 'ld' using the -l option. Foreign function era 🌍
  • --link_code S β€” link-files to be linked together to form an executable.
  • --link_exe S, -ldexe S β€” specifies the command used for linking an executable. The standard is to use 'gcc' for linking. When linking with c++ libraries, 'g++' is the linker you want. On Linux the default is 'gcc', whereas on macOS systems, the default is

(and that's genuinely where the sentence stops in the page β€” we love a cliffhanger 😭)

  • --link_shared S, -ldshared S β€” specifies the command used for linking a shared object file. The standard is to use 'gcc' for linking.
  • --link_time_dead_code_elimination, -ltdce β€” link time dead code elimination.
  • --load_basis_files S, -load S β€” basis files to be loaded before compilation proper. Get your bases loaded first, always 🧚
  • --log_to_file β€” log to files instead of stdout. Quiet mode, mysterious mode πŸ¦‹
  • --man β€” print man-page and exit. You are here πŸ“
  • --maximum_inline_size N, -max_inl_sz N β€” Bestie, any function smaller than this size (counted in abstract syntax tree nodes) gets inlined, even if it's used more than once. Functions used only once are always inlined. A function declared in one program unit may be inlined when applied in another program unit as long as it's sufficiently closed (refers only to exported identifiers) and the option --cross_opt is enabled. ✨
  • --maximum_specialise_size N, -max_spec_sz N β€” Function-parameterised functions smaller than this size (counted in abstract syntax tree nodes) are specialised if all applications of the function within its own body are applied to its formal function argument, even if they're used more than once. Functions used only once are specialised no matter their size. A function declared in one program unit may be specialised when applied in another program unit as long as it's sufficiently closed (refers only to exported identifiers) and the option --cross_opt is enabled. Also see the option --specialize_recursive_functions. πŸŽ€
  • --messages β€” Print messages about reading source files and generating target files. 🫢
  • --minimize_fixs β€” Minimize fix constructs (Lambda Expression Optimiser). πŸ’…
  • --mlb-subdir S β€” For ensuring that the smart recompilation scheme is not reusing target-code compiled with different settings, a string provided with the mlb-subdir option can ensure the use of consistently generated code. This option is Useful, in particular, when performing benchmarking. πŸ¦‹
  • --mlb_path_maps S, -mlb-path-map S β€” ML Basis path map files to be used. 🌸
  • --namebase S β€” Name base to enforce unique names when compiling mlb-files. πŸŽ€
  • --no_aggressive_opt, -no_aopt β€” Opposite of --aggressive_opt, -aopt. πŸ™ˆ
  • --no_constant_folding, -no_cfold β€” Opposite of --constant_folding, -cfold. ✨
  • --no_contract β€” Opposite of --contract. πŸ’œ
  • --no_cross_module_opt, -no_cross_opt β€” Opposite of --cross_module_opt, -cross_opt. πŸ¦‹
  • --no_dangling_pointers, -no_dangle β€” Opposite of --dangling_pointers, -dangle. ⭐
  • --no_delete_target_files β€” Opposite of --delete_target_files. 🌈
  • --no_drop_unused_funargs, -no_dufa β€” Opposite of --drop_unused_funargs, -dufa. πŸ’–
  • --no_eliminate_explicit_records β€” Opposite of --eliminate_explicit_records. 🧚
  • --no_fix_floating β€” Opposite of --fix_floating. πŸ“
  • --no_high_pointer_tagging β€” Opposite of --high_pointer_tagging. πŸ”₯
  • --no_import_basislib, -no_basislib β€” Opposite of --import_basislib, -basislib. πŸ‘‘
  • --no_link_time_dead_code_elimination, -no_ltdce β€” Opposite of --link_time_dead_code_elimination, -ltdce. πŸ’€
  • --no_messages β€” Opposite of --messages. 🌸
  • --no_minimize_fixs β€” Opposite of --minimize_fixs. πŸ’…
  • --no_optimiser, -no_opt β€” Opposite of --optimiser, -opt. ✨
  • --no_preserve_tail_calls, -no_ptc β€” Opposite of --preserve_tail_calls, -ptc. 🫢
  • --no_print_aux_reset, -no_Paux β€” Opposite of --print_aux_reset, -Paux. πŸ¦‹
  • --no_print_control_abbrev_layout, -no_abbrev β€” Opposite of --print_control_abbrev_layout, -abbrev. πŸŽ€
  • --no_print_regions, -no_Pregions β€” Opposite of --print_regions, -Pregions. 🌈
  • --no_raggedRight β€” Opposite of --raggedRight. ⭐
  • --no_region_inference, -no_ri β€” Opposite of --region_inference, -ri. πŸ’œ
  • --no_register_allocation β€” Opposite of --register_allocation. 🧚
  • --no_specialize_recursive_functions β€” Opposite of --specialize_recursive_functions. πŸ”₯
  • --no_type_check_lambda β€” Opposite of --type_check_lambda. πŸ’–
  • --no_unbox_funargs β€” Opposite of --unbox_funargs. πŸ“
  • --no_unbox_real_funargs β€” Opposite of --unbox_real_funargs. 🌸
  • --no_unbox_reals β€” Opposite of --unbox_reals. ✨
  • --no_uncurrying, -no_uncurry β€” Opposite of --uncurrying, -uncurry. πŸŽ€
  • --objs β€” If enabled, MLKit writes object-file paths to the file run or the file specified by -output. The path to the runtime system (archive file) is included. The option is best used together with the option -no_delete_target_files. 🫢
  • --optimiser, -opt β€” Enable optimisation of intermediate language code (Lambda Expressions). Which optimisations are performed is controlled by individual flags. The optimisations include function inlining, function specialisation, fix-minimization, unboxing of function arguments, and elimination of unnecessary record constructions. πŸ’…
  • --output S, -o S β€” The name of the executable file generated by the Kit. πŸ‘‘
  • --parallel_compilation N, -j N β€” The maximum number of parallel processes used for compilation. ⚑
  • --parallelism, -par β€” When enabled, the runtime system supports parallel threads. 🧡
  • --parallelism_alloc_unprotected, -par0 β€” When enabled, allocation into a region is not guaranteed to be atomic. ⚠️
  • --preserve_tail_calls, -ptc β€” Avoid the wrapping of letregion constructs around tail calls. Turning on garbage collection automatically turns on this option. 🌈
  • --pretty_depth N β€” This flag controls the pretty-printing depth of values printed in the REPL. The value must be an integer larger than zero. πŸ”’
  • --pretty_string_size N β€” This flag controls the pretty-printing size of strings printed in the REPL. The value must be an integer larger than zero. πŸŽ€
  • --print_K_normal_forms β€” Print Region Expressions in K-Normal Form. Applicable only after storage mode analysis has been applied. ✨
  • --print_all_program_points, -Ppp β€” Print all program points when printing physical size inference expressions. πŸ¦‹
  • --print_aux_reset, -Paux β€” Print resetting of auxiliary regions associated with construction of nullary constructor values. This flag affects the MulExp pretty printer. πŸ’œ
  • --print_bit_vectors β€” No description on the page β€” just the flag itself, no invented lore πŸ™ˆ.
  • --print_calc_offset_program β€” No description on the page β€” just the flag itself, no invented lore πŸ™ˆ.
  • --print_call_explicit_expression, -Pcee β€” Print Region Expression with call annotations. 🌸
  • --print_clos_conv_program, -Pccp β€” Print Region Expression after closure conversion. 🧚
  • --print_closed_export_bases, -Pceb β€” Controls printing of closed export bases. ⭐
  • --print_constraints β€” Print ReML effect constraints when printing region and effect variables. πŸ”₯
  • --print_control_abbrev_layout, -abbrev β€” Abbreviate layout of multiplicity expressions and call- explicit expressions. For instance, do not show at- annotations for top-level functions, do not show at- annotations for immediate constants, do not show region- bindings for zero-size regions that are associated only with immediate constants, do not show empty formal and actual region parameter lists, do not show 'funcall', and do not show unique id for explicit region variables or explicit effect variables. πŸ’…
  • --print_control_prefix_infix β€” Prefix infix operations with module identifier to further indicate the type of the operation. πŸŽ€
  • --print_drop_regions_expression, -Pdre β€” Print Region Expression after dropping word regions and region arguments with only get-effects. πŸ¦‹
  • --print_drop_regions_expression_with_storage_modes, -Pdresm β€” Print Region Expression after dropping word regions and region arguments with only get-effects. Also print atbot and attop annotations resulting from storage mode analysis. ✨
  • --print_effects, -Peffects β€” Print effects in region types. 🌈
  • --print_excon_name β€” Print underlying unique name when printing excons. πŸ’œ
  • --print_export_bases, -Peb β€” Controls printing of export bases. ⭐
  • --print_fetch_and_flush_program β€” Print program with instructions for activation record fetching and flushing. 🧚
  • --print_linearised_program β€” Print a linearlised representation of the program unit. πŸ“
  • --print_lvar_name β€” Print underlying unique name when printing lvars. 🌸
  • --print_normalized_program β€” Print Region Expression after K-normalisation. πŸŽ€
  • --print_opt_lambda_expression, -Pole β€” Print Lambda Expression after optimisation. πŸ”₯
  • --print_physical_size_inference_expression, -Ppse β€” Print Region Expression after physical size inference. πŸ’–
  • --print_post_elab_ast, -Ppeast β€” Print ast after elaboration. πŸ¦‹
  • --print_region_flow_graph, -Prfg β€” Print a region flow graph for the program fragment and generate a .vcg-file, which can be viewed using the xvcg program. ⭐
  • --print_region_inferred_program, -Prip β€” Print region-inferred program. 🌈
  • --print_region_spreaded_program, -Prsp β€” Print region-spreaded program. πŸ’œ
  • --print_region_static_env0, -Prse0 β€” Print imported region static environment prior to region inference. 🧚
  • --print_regions, -Pregions β€” Print region variables in types and expressions. 🌸
  • --print_register_allocated_program β€” No description on the page β€” just the flag itself, no invented lore πŸ™ˆ.
  • --print_rho_levels β€” Print levels of region and effect variables in types and intermediate forms. Levels control quantification of region and effect variables. πŸŽ€
  • --print_rho_protection, -Prho_protection β€” Print protectedness of region variables if set (P or U). πŸ”₯
  • --print_rho_types β€” Print region types of region variables in types and intermediate forms. Possible region types are:
    • p β€” Type of regions containing pairs.
    • a β€” Type of regions containing arrays.
    • r β€” Type of regions containing references.
    • t β€” Type of regions containing triples.
    • s β€” Type of regions containing strings.
    • T β€” Type of regions containing other than the above kinds of values. ✨
  • --print_simplified_program β€” Print simplified program after register allocation. πŸ’…
  • --print_storage_mode_expression, -Psme β€” Print Region Expression after storage mode analysis. πŸ¦‹
  • --print_type_name_stamps, -Ptypestamps β€” Print type name stamps and their attributes in types and expressions. ⭐
  • --print_types, -Ptypes β€” Print types when printing intermediate forms. For Lambda Expressions, ordinary ML types are printed, whereas for Region Expressions, region types are printed. 🌈
  • --raggedRight β€” Use ragged right margin in pretty-printing of expressions and types. πŸŽ€
  • --recompile_basislib, -scratch β€” Recompile basis library from scratch. This option is useful together with other options that control code generation. πŸ’œ
  • --region_inference, -ri β€” With this flag disabled, all values are allocated in global regions. 🧚
  • --region_profiling, -prof β€” turns on region profiling ✨ Object code that comes from compiling a program with region profiling enabled gets instrumented with profiling information. Then, when you actually run a program compiled that way, it produces a profile file called run.rp, and you can feed that to the profiling tool rp2ps that ships with the MLKit to get profiling graphs in various forms. it's giving data visualization πŸ’…
  • --register_allocation β€” do register allocation. Turn this off and your programs run somewhat slower β€” but like, they still run, and you save about 15 percent on compile time πŸŽ€
  • --reml β€” ReML is Standard ML with support for programming with explicit regions, explicit effects, and effect constraints. With ReML, atomic effects also include mutation effects. And here's the fine print bestie: whereas ReML includes parallel thread support, currently, ReML does not support integration with reference-tracing garbage collection πŸ™ˆ
  • --report_boxities β€” report, for every datatype declaration, the inferred boxity (representation) of its value constructors. receipts for your datatypes πŸ“‹
  • --report_file_sig, -sig β€” report signatures for each file read.
  • --safeLinkTimeElimination β€” treat this module as a library in the sense that the code can be eliminated if it's not used, even if the code has side effects πŸ‘€ yes that's exactly what it says, no cap.
  • --specialize_recursive_functions β€” specialise recursive functions. Use the option maximum_specialise_size to control which functions get specialised. And if this flag is on, functions that are applied only once are specialised, no matter the setting of --maximum_specialise_size (Lambda Expression Optimiser) πŸ”₯
  • --statistics_after_optimisation, -stats_opt β€” report optimisation statistics after optimisation of Lambda Expression. numbers!! we love numbers ⭐
  • --strip β€” if enabled, MLKit strips the generated executable βœ‚οΈ
  • --type_check_lambda β€” type check lambda expression prior to performing region inference. Type checking is very fast, and for normal use you should not disable this option. Type checking intermediate forms is very powerful for eliminating bugs in the compiler β€” lowkey iconic 🧚
  • --unbox_funargs β€” unbox arguments to fix-bound functions, for which the argument 'a' is used only in contexts '#i a'. All call sites get transformed to match the new function (Lambda Expression Optimiser).
  • --unbox_real_funargs β€” unbox arguments of type real to fix-bound functions, for which the argument 'a' is used only in contexts that unboxes 'a'. All call sites are transformed to match the new function. Heads up: this optimisation has effect only when the flags '-unbox_funargs' and...
okay so the sentence literally trails off right there in the original manual 😭 "and" and then nothing. not me inventing the rest β€” I would never. mysteries of the manpage πŸ•΅οΈβ€β™€οΈ
  • --unbox_reals β€” unbox real values and computations on real values inside functions. Real values stored in data structures and passed to functions are still boxed though, so don't get too excited πŸ“
  • --uncurrying, -uncurry β€” enable uncurrying of curried functions. The uncurried function takes its arguments unboxed in registers or on the stack. For partial applications and non-application uses of the function, appropriate eta-expansions are applied ✨
  • --version, -v, -V β€” print version information and exit. that's it. that's the whole vibe check πŸ‘‘
  • --warn_on_escaping_puts β€” enables the compiler to issue a warning whenever a region type scheme contains a put effect on a region that is not quantified 🚨
  • --warn_on_parallel_puts β€” enables the compiler to issue a warning whenever a par-construct is passed functions with intersecting put effects 🚨🚨
  • --width N, -w N β€” column width used when pretty printing intermediate code. give it a number, bestie πŸ’…

πŸ¦‹ EXIT STATUS πŸ¦‹

Exits with status 0 on success and -1 on failure. that's the whole story β€” no dramatic third option, no plot twist 😌


🌈 ENVIRONMENT 🌈

A library install directory must be provided in an environment variable SML_LIB, as a path-definition in the user's personal path-map ~/.reml/mlb-path-map, or in a system wide path-map /nix/store/sfp5bfgah1f35wd1r96xrvhzx6nir1r6-mlkit-4.7.23/etc/reml/mlb-path-map.

Like, you gotta give it one of those three. it's not optional, fr fr 🫢


πŸŽ€ FILES πŸŽ€

  • /nix/store/sfp5bfgah1f35wd1r96xrvhzx6nir1r6-mlkit-4.7.23/etc/reml/mlb-path-map β€” system-wide configuration of library and runtime system locations
  • ~/.reml/mlb-path-map β€” user specific configuration of library and runtime system locations

one for everyone, one just for you πŸ’–


πŸ‘‘ CREDITS πŸ‘‘

ReML was developed by Martin Elsman. Many people have helped developing the MLKit on which ReML is built; see the MLKit home page for details. shoutout to the whole team honestly πŸ™Œ


πŸ’œ SEE ALSO πŸ’œ

See the MLKit manual "Programming with Regions in the MLKit", available from the MLKit home page

http://melsman.github.io/mlkit

for an in-depth introduction to programming with regions in the MLKit. 🌸

The home page also provides an overview of which parts of the Standard ML Basis Library the MLKit implements, along with download and installation instructions.

go read it, it's giving required reading for the girlies who want to actually understand regions πŸ“šβœ¨


that's a wrap on reml(1)!! πŸ¦‹ this gorgeousness is version v4.7.23, and yes it's filed under reml(1) in that very section of the manual β€” mwah, love u, go compile something πŸ’…πŸŽ€πŸ’–

πŸ“¦ where this page comes from