I had some issues setting up millet to analize the lunarml libraries and it turns out I just needed to add the path to lunarml's lib (pretty straightforward) but I also needed to setup TARGET_LANG in the millet.toml file (not that straightforward).
I know that it regards mostly integration with an external tool to this project but millet is the only SML language server, as far as I know at least.
[workspace.path-vars]
SML_LIB = { value = "my/sml/lib/path" }
TARGET_LANG = { value = "luajit" }
I guess its something most people would eventually figure out but having these things documented always makes for a nicer dev experience and helps with adoption, especially with how limited the SML ecosystem is in terms of tooling.
Also I see theres mention of this in issue #9 so this config should address that too.
If theres a need for help writing this down in an editor setup section or something I wouldn't mind do it myself.
I had some issues setting up millet to analize the lunarml libraries and it turns out I just needed to add the path to lunarml's lib (pretty straightforward) but I also needed to setup
TARGET_LANGin themillet.tomlfile (not that straightforward).I know that it regards mostly integration with an external tool to this project but millet is the only SML language server, as far as I know at least.
I guess its something most people would eventually figure out but having these things documented always makes for a nicer dev experience and helps with adoption, especially with how limited the SML ecosystem is in terms of tooling.
Also I see theres mention of this in issue #9 so this config should address that too.
If theres a need for help writing this down in an editor setup section or something I wouldn't mind do it myself.