Publish to crates.io

[filmor]

At least for devs you could simplify the installation by just publishing your crates to crates.io via the normal mechanisms. gleam is already taken, but maybe something like gleam-lang would suite you. That way installation for anyone who has rust installed would just be cargo install gleam-lang.

[lpil]

Good suggestion! For now it can be installed like so:

cargo install --git https://github.com/lpil/gleam --tag v0.4.1

[stefanluptak]

I have no experience with crates.io, but I assume we're able to do this automatically after a release is published. Am I right? If yes, I can implement this.

[lpil]

I've not yet looked into this as using cargo's git support works for now. I expect you're right. :)

[filmor]

If you don't have super-frequent releases, just do it manually. It's just running cargo publish.

[stefanluptak]

[lpil]

There is some info here. https://rust-lang-nursery.github.io/cli-wg/tutorial/packaging.html

I'll try this manually for the next release and then we can automate after.

[tclain]

That would be a great use case to develop tooling against a stable interface.

For instance to develop a lsp server, a hint suggester..., we need to have access to the parser, AST and so on. It seems less intimidating to incubate that as a separate package and once we reach maturity to merge it as a subcommand.

IMHO nimsuggest and nim-lsp are a good example of that.

[lpil]

That's a great use case, but these APIs are not at all stable and there are often major internal changes with patch versions of Gleam. The cost of stablising compiler internals would be far too great for this early stage.

On the bright side I intend to build the LSP into the compiler itself, so breaking changes will be much less of an issue.